{
  "data": {
    "a": {
      "slug": "metronome",
      "name": "Metronome",
      "vendor": "Metronome (Stripe)",
      "vendorUrl": "https://metronome.com",
      "kind": "http-api",
      "category": "payment-platforms",
      "summary": "Metronome is a hosted usage-based billing platform, part of Stripe. Its REST API ingests usage events, defines billable metrics, rate cards and contracts, and generates invoices, with official SDKs for Python, Node.js, Go, Ruby and Java.",
      "url": "https://www.anchorterminal.com/tools/metronome",
      "markdownUrl": "https://www.anchorterminal.com/tools/metronome.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/metronome.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/metronome.json",
      "repo": "https://github.com/Metronome-Industries/metronome-node",
      "license": "Proprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.metronome.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@metronome/sdk"
        },
        {
          "registry": "pypi",
          "name": "metronome-sdk"
        },
        {
          "registry": "go",
          "name": "github.com/Metronome-Industries/metronome-go"
        }
      ],
      "auth": "api-key",
      "authNotes": "Bearer tokens, created by a person under Developer, API tokens in the Metronome app and shown once. A sandbox token reaches only sandbox data and a production token only production data. A token has its creator's permissions unless Metronome support scopes it by access level, environment or endpoint. Tokens can be archived, not edited. The API description also describes agentic tokens, whose writes need a person's approval.",
      "pricing": "usage",
      "pricingNotes": "The Startup plan costs 0.8 per cent of billing volume plus $0.04 per 1,000 ingested events, self-serve with a credit card for production. The pricing page says \"Start free\" and a sandbox account is self-serve. Custom plan prices are set by sales, and the docs describe an annual platform fee plus consumption charges on order forms (https://metronome.com/pricing, checked 2026-10-09).",
      "priceSummary": "0.8% fee",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the OpenAPI description, the docs index or the pricing page (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 7,
        "npmWeekly": 363390,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.metronome.com/guides/get-started/home",
      "llmsTxt": "https://docs.metronome.com/llms.txt",
      "openapi": "https://docs.metronome.com/openapi.json",
      "capabilities": [
        "payments.metering",
        "accounting.invoices"
      ],
      "tags": [
        "hosted",
        "usage-billing",
        "openapi",
        "llms-txt",
        "webhooks",
        "python",
        "typescript",
        "go",
        "ruby",
        "java",
        "status-page",
        "soc2",
        "closed-source",
        "sandbox"
      ],
      "lastRelease": "2026-09-29",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.7,
        "grade": "B",
        "agentReady": false,
        "rank": 173,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 4,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 82,
          "payments": 39,
          "reliability": 68,
          "schema": 88,
          "security": 68,
          "transparency": 65
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "Metronome's API carries an `Idempotency-Key` on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a `message` string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026.",
        "bestFor": "A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces.",
        "strengths": [
          "Public OpenAPI 3.0.1 description with 142 operations and 509 schemas, plus llms.txt and a Markdown twin of each docs page",
          "`Idempotency-Key` accepted on every POST for at least 24 hours, `uniqueness_key` on contracts and alerts, and event `transaction_id` deduplication for 34 days",
          "Agentic tokens get `403 AgenticMutationBlocked` on writes and queue them at `/v1/approval_requests` for a person to approve or deny",
          "Audit log readable at `/v1/auditLogs`, naming the user or API token, the resource, the action, the IP address and the user agent",
          "Startup plan prices are public (0.8 per cent of billing volume and $0.04 per 1,000 ingested events), with a self-serve sandbox sign-up"
        ],
        "weaknesses": [
          "Errors are a single `message` string with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations",
          "Token scoping by access level, environment or endpoint is set by contacting support. By default a token has its creator's permissions",
          "The status feed lists 13 incidents between 22 July and 8 October 2026, among them two hours of elevated API and ingest errors on 3 September",
          "No SLA document is published. The pricing page names enhanced SLAs on the Custom plan only",
          "The governing terms are Stripe's Services Agreement, which does not name Metronome and grants Stripe a licence to use customer content to develop and improve its services",
          "No deprecation policy was found. SDK releases of 16 January and 2 March 2026 removed fields, announced in the changelog on the day"
        ],
        "agentNotes": [
          "Send an `Idempotency-Key` header on every POST and reuse it on retry. A cached error is returned for the same key, so use a new key after fixing the cause",
          "Give each usage event a stable `transaction_id`. Metronome ignores repeats for 34 days and accepts at most 100 events per `/v1/ingest` call",
          "On 429 read `X-Metronome-Rate-Limit-Type` (`client` or `customer`) and back off. Unlisted endpoints default to 8 requests a second",
          "With an agentic token, expect `403 AgenticMutationBlocked` on writes. Post the original method, path and body to `/v1/approval_requests` and show the person the `approval_url`",
          "Use a sandbox token for testing. The token alone decides whether a call reaches sandbox or production data"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 69.7
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 82,
          "payments": 39,
          "reliability": 68,
          "schema": 88,
          "security": 68,
          "transparency": 45
        },
        "provenanceScore": 85
      },
      "connect": {
        "install": "npm install @metronome/sdk",
        "http": "curl -X POST https://api.metronome.com/v1/billable-metrics/create \\\n  -H \"Authorization: Bearer $METRONOME_API_TOKEN\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"name\": \"API Calls\",\n    \"aggregation_type\": \"count\",\n    \"event_type_filter\": {\n      \"in_values\": [\"api_call\"]\n    }\n  }'"
      },
      "letme": {
        "capability": "https://letme.dev/payments.metering",
        "tool": "https://letme.dev/metronome"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Startup plan fee on billing volume",
          "unit": "pct",
          "usd": 0.8,
          "note": "plus the event fee. Custom plan priced by sales"
        },
        {
          "item": "Ingested usage event on the Startup plan",
          "unit": "tx",
          "usd": 0.00004,
          "note": "$0.04 per 1,000 ingest events"
        }
      ],
      "provenance": {
        "legalEntity": "Stripe, LLC",
        "domain": "metronome.com",
        "domainRegistered": "1998-11-04",
        "endpointOnVendorDomain": true,
        "terms": "https://stripe.com/legal/ssa",
        "privacy": "https://stripe.com/privacy",
        "statusPage": "https://status.metronome.com",
        "changelog": "https://docs.metronome.com/changelog",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "Metronome's site says it is now part of Stripe. Its legal centre links two documents, Stripe's Services Agreement as terms of service and Stripe's privacy policy.",
          "The Stripe Services Agreement (General Terms last modified 28 September 2026) names Stripe, LLC as the contracting entity for the United States, with other Stripe entities by country. It does not mention Metronome by name. Our request was redirected to the United Kingdom edition of the page.",
          "The Stripe privacy policy was last updated on 28 April 2026 and covers services supplied under the Stripe Services Agreement. It does not mention Metronome by name.",
          "The API answers at https://api.metronome.com per the OpenAPI description's server entry.",
          "https://metronome.com/.well-known/security.txt returned 404. The SDK repositories' SECURITY.md gives dev-feedback@metronome.com for service security questions.",
          "RDAP for metronome.com gives a registration date of 1998-11-04, which predates the company."
        ],
        "score": 85
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/metronome.json",
      "live": {
        "slug": "metronome",
        "probe": {
          "target": "https://api.metronome.com",
          "method": "get",
          "lastAt": "2026-10-10T02:55:02.229219584Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 427,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 427,
          "p95ms24h": 510,
          "samples24h": 115,
          "samples30d": 115,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.metronome.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-10T02:50:27.569689356Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "Metronome-Industries/metronome-node",
            "version": "v3.10.0",
            "released": "2026-07-23",
            "seenAt": "2026-10-09T17:05:18.814448022Z"
          },
          {
            "registry": "npm",
            "name": "@metronome/sdk",
            "version": "3.10.0",
            "seenAt": "2026-10-09T17:05:16.810932336Z"
          },
          {
            "registry": "pypi",
            "name": "metronome-sdk",
            "version": "4.11.1",
            "released": "2026-08-28",
            "seenAt": "2026-10-09T17:05:17.824671392Z"
          }
        ],
        "githubStars": 7,
        "npmWeekly": 363390,
        "pypiWeekly": 157134,
        "pages": [
          {
            "url": "https://docs.metronome.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:37:46.155976649Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "db085f3c5807"
          },
          {
            "url": "https://metronome.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:42:03.074548835Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "0590b21f8bad"
          },
          {
            "url": "https://stripe.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:09.307033961Z",
            "changedAt": "2026-10-08T18:24:56.248781585Z",
            "fingerprint": "73ea5b705ed5"
          },
          {
            "url": "https://stripe.com/legal/ssa",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:05.029930659Z",
            "changedAt": "2026-10-08T18:24:51.983854093Z",
            "fingerprint": "43483f64e8ca"
          }
        ],
        "updatedAt": "2026-10-10T02:55:02.229219584Z"
      }
    },
    "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Metronome leads on reliability.",
    "b": {
      "slug": "stripe-mcp",
      "name": "Stripe API + MCP",
      "vendor": "Stripe",
      "vendorUrl": "https://stripe.com",
      "kind": "http-api",
      "category": "payment-platforms",
      "summary": "Card, stablecoin and billing APIs with a hosted MCP server (mcp.stripe.com, 10 tools including generic stripe_api_read and stripe_api_write).",
      "url": "https://www.anchorterminal.com/tools/stripe-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json",
      "repo": "https://github.com/stripe/ai",
      "license": "MIT",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api.stripe.com/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "stripe"
        },
        {
          "registry": "npm",
          "name": "@stripe/mcp"
        },
        {
          "registry": "npm",
          "name": "@stripe/agent-toolkit"
        },
        {
          "registry": "pypi",
          "name": "stripe-agent-toolkit"
        },
        {
          "registry": "npm",
          "name": "@stripe/ai-sdk"
        },
        {
          "registry": "npm",
          "name": "@stripe/token-meter"
        }
      ],
      "auth": "mixed",
      "authNotes": "API takes a secret or restricted key as Bearer (or Basic). MCP takes OAuth for interactive clients (per-account and sandbox permissions, revocable sessions) or an Agent API key as Bearer for autonomous clients. Stripe-Account header for Connect platforms. From 2026-10-31 the MCP server rejects full-access secret keys and non-Agent restricted keys with a 401 OAuth challenge.",
      "pricing": "usage",
      "pricingNotes": "No charge for the MCP server or the toolkit, and no setup or monthly fees. US cards 2.9% + 30 cents per successful charge. Stablecoin payments 1.5% (including conversion, screening and gas sponsorship). Billing 0.7% of billing volume, or from $620 a month on a one-year contract. Shared payment tokens for agent card payments cost $0.15 per token issued. Stablecoin acceptance is open to US businesses outside New York and by request in 30+ countries (https://stripe.com/pricing).",
      "priceSummary": "2.9% fee",
      "where": "both",
      "x402": {
        "level": "partial",
        "evidence": "Stripe merchants can accept x402 payments in USDC on Base and have them recorded as PaymentIntents. The MCP server and the Stripe API themselves don't take x402 payment (https://docs.stripe.com/payments/machine/x402).",
        "endpoints": []
      },
      "toolCount": 10,
      "popularity": {
        "githubStars": 1848,
        "npmWeekly": 15284,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.stripe.com/agents",
      "llmsTxt": "https://docs.stripe.com/llms.txt",
      "openapi": "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json",
      "registryName": "com.stripe/mcp",
      "capabilities": [
        "payments.card",
        "payments.stablecoin",
        "payments.x402",
        "payments.metering",
        "payments.checkout",
        "payments.payouts"
      ],
      "tags": [
        "official",
        "hosted",
        "local",
        "open-source",
        "oauth",
        "confirmation",
        "mcp",
        "llms-txt",
        "openapi",
        "stablecoin",
        "x402",
        "webhooks",
        "typescript",
        "python"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 82.4,
        "grade": "A",
        "agentReady": true,
        "rank": 5,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 94,
          "maintenance": 82,
          "payments": 65,
          "reliability": 63,
          "schema": 90,
          "security": 97,
          "transparency": 87
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "high",
          "date": "2026-10-04"
        },
        "negative": 0,
        "verdict": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.",
        "bestFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.",
        "strengths": [
          "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat",
          "OAuth with per-account and per-environment permissions, Agent-tagged restricted keys, and revocable sessions",
          "Human approval for sensitive `stripe_api_write` actions such as refunds and outbound payments",
          "Rate limits, 429 reasons, backoff guidance and idempotency keys all documented",
          "Public OpenAPI spec, dated API versions and a HackerOne bug bounty"
        ],
        "weaknesses": [
          "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins",
          "Stablecoin acceptance needs manual approval, excludes New York and is by email request outside the US",
          "Generic `stripe_api_read` and `stripe_api_write` tools push method choice and parameters onto the agent",
          "The official MCP registry entry is 0.2.4 from October 2025 and names an old repo",
          "Status history renders only in JavaScript"
        ],
        "agentNotes": [
          "Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401",
          "Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right",
          "When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours",
          "Send an `Idempotency-Key` on every create so a retry can't charge twice",
          "On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 8,
        "avgRating": 4,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "high",
            "grade": "A",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 82.4
          }
        ],
        "editorialScores": {
          "ergonomics": 94,
          "maintenance": 82,
          "payments": 65,
          "reliability": 63,
          "schema": 90,
          "security": 97,
          "transparency": 78
        },
        "provenanceScore": 95
      },
      "connect": {
        "http": "curl https://api.stripe.com/v1/balance -H \"Authorization: Bearer $STRIPE_SECRET_KEY\"",
        "claudeCode": "claude mcp add --transport http stripe https://mcp.stripe.com",
        "config": {
          "mcpServers": {
            "stripe": {
              "headers": {
                "Authorization": "Bearer ${STRIPE_AGENT_KEY}"
              },
              "url": "https://mcp.stripe.com"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/payments.card",
        "tool": "https://letme.dev/stripe-mcp"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "US card payment",
          "unit": "pct",
          "usd": 2.9,
          "note": "plus 30 cents per successful charge"
        },
        {
          "item": "US card payment fixed fee",
          "unit": "tx",
          "usd": 0.3
        },
        {
          "item": "Stablecoin payment",
          "unit": "pct",
          "usd": 1.5
        },
        {
          "item": "Billing",
          "unit": "pct",
          "usd": 0.7,
          "note": "of billing volume"
        }
      ],
      "provenance": {
        "legalEntity": "Stripe, LLC",
        "domain": "stripe.com",
        "domainRegistered": "1995-09-12",
        "domainNote": "stripe.com was registered in 1995, before Stripe bought it.",
        "endpointOnVendorDomain": true,
        "terms": "https://stripe.com/legal/ssa",
        "privacy": "https://stripe.com/privacy",
        "statusPage": "https://status.stripe.com",
        "changelog": "https://docs.stripe.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-09-30",
        "score": 95
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/stripe-mcp.json",
      "live": {
        "slug": "stripe-mcp",
        "probe": {
          "target": "https://api.stripe.com/v1",
          "method": "get",
          "lastAt": "2026-10-10T02:55:11.84356616Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 73,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 56,
          "p95ms24h": 124,
          "samples24h": 249,
          "samples30d": 3420,
          "days": [
            {
              "date": "2026-09-27",
              "probes": 132,
              "ok": 132
            },
            {
              "date": "2026-09-28",
              "probes": 285,
              "ok": 285
            },
            {
              "date": "2026-09-29",
              "probes": 286,
              "ok": 286
            },
            {
              "date": "2026-09-30",
              "probes": 286,
              "ok": 286
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 276
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 268
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.stripe.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:18.159348435Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.stripe/mcp",
            "version": "0.2.4",
            "seenAt": "2026-10-09T02:57:46.004536428Z"
          },
          {
            "registry": "npm",
            "name": "@stripe/agent-toolkit",
            "version": "0.9.0",
            "seenAt": "2026-10-09T17:22:23.136555078Z"
          },
          {
            "registry": "npm",
            "name": "@stripe/ai-sdk",
            "version": "0.1.3",
            "seenAt": "2026-10-09T17:22:25.502513825Z"
          },
          {
            "registry": "npm",
            "name": "@stripe/mcp",
            "version": "0.3.3",
            "seenAt": "2026-10-09T17:22:21.151998994Z"
          },
          {
            "registry": "npm",
            "name": "@stripe/token-meter",
            "version": "0.1.0",
            "seenAt": "2026-10-09T17:22:27.344205843Z"
          },
          {
            "registry": "npm",
            "name": "stripe",
            "version": "23.0.0",
            "seenAt": "2026-10-09T17:22:20.89644214Z"
          },
          {
            "registry": "pypi",
            "name": "stripe-agent-toolkit",
            "version": "0.7.0",
            "released": "2026-02-12",
            "seenAt": "2026-10-09T17:22:25.305272702Z"
          }
        ],
        "githubStars": 1866,
        "npmWeekly": 23282402,
        "pypiWeekly": 2172,
        "securityTxt": {
          "url": "https://stripe.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2026-12-31T23:59:00.000Z",
          "checkedAt": "2026-10-09T15:40:09.920948203Z"
        },
        "llmsTxt": {
          "url": "https://docs.stripe.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:51.241783072Z"
        },
        "domain": {
          "domain": "stripe.com",
          "registered": "1995-09-12",
          "source": "https://rdap.verisign.com/com/v1/domain/stripe.com",
          "checkedAt": "2026-10-04T13:06:58.944197161Z"
        },
        "pages": [
          {
            "url": "https://docs.stripe.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:38:24.633373695Z",
            "changedAt": "2026-10-07T18:05:30.851845677Z",
            "fingerprint": "1accebcd47a8"
          },
          {
            "url": "https://docs.stripe.com/mcp",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-10-09T18:38:28.452313533Z",
            "changedAt": "2026-10-08T18:19:33.638425552Z",
            "fingerprint": "73c755c5cd0f"
          },
          {
            "url": "https://stripe.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:56.248781585Z",
            "changedAt": "2026-10-08T18:24:56.248781585Z",
            "fingerprint": "73ea5b705ed5"
          },
          {
            "url": "https://stripe.com/legal/ssa",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:24:51.983854093Z",
            "changedAt": "2026-10-08T18:24:51.983854093Z",
            "fingerprint": "43483f64e8ca"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.stripe.com",
          "checkedAt": "2026-09-29T21:56:38.06237447Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-09-28T21:55:54.756223507Z"
        },
        "updatedAt": "2026-10-10T02:55:11.84356616Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Metronome (Stripe)",
        "b": "Stripe",
        "name": "Vendor"
      },
      {
        "a": "https://api.metronome.com",
        "b": "https://api.stripe.com/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "payer tooling only",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0",
        "b": "MIT",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "10",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.stripe/mcp",
        "name": "MCP registry"
      },
      {
        "a": "2026-09-29",
        "b": "2026-09-30",
        "name": "Last release"
      },
      {
        "a": "2026-09-28",
        "b": "2026-09-28",
        "name": "Terms last updated"
      },
      {
        "a": "2026-04-28",
        "b": "2026-04-28",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "7 stars, 363k npm/wk",
        "b": "1.8k stars, 15k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "4/5 (8)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Metronome leads on reliability.",
        "question": "Which is better for AI agents, Metronome or Stripe API + MCP?"
      },
      {
        "answer": "Metronome needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.",
        "question": "Do Metronome and Stripe API + MCP need an API key?"
      },
      {
        "answer": "Yes. Metronome has a hosted endpoint at https://api.metronome.com and Stripe API + MCP at https://api.stripe.com/v1.",
        "question": "Can an agent call Metronome and Stripe API + MCP without installing anything?"
      },
      {
        "answer": "No open-source release is listed for Metronome. Stripe API + MCP is open source (MIT).",
        "question": "Are Metronome and Stripe API + MCP open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 68 against 63"
        ],
        "also": null,
        "goodFor": "A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces.",
        "slug": "metronome",
        "watchFor": "Errors are a single `message` string with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 94 against 75",
          "Security \u0026 auth, 97 against 68",
          "Payments \u0026 pricing, 65 against 39",
          "Transparency \u0026 trust, 87 against 65"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Runs on your own machine",
          "Open source"
        ],
        "goodFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.",
        "slug": "stripe-mcp",
        "watchFor": "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins"
      }
    ],
    "job": {
      "capability": "payments.metering",
      "name": "Usage billing"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/atxp-vs-metronome.json",
        "title": "ATXP vs Metronome",
        "url": "https://www.anchorterminal.com/compare/atxp-vs-metronome"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lago-vs-metronome.json",
        "title": "Lago vs Metronome",
        "url": "https://www.anchorterminal.com/compare/lago-vs-metronome"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.json",
        "title": "Lago vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-nevermined.json",
        "title": "Metronome vs Nevermined API + MCP",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-nevermined"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-orb.json",
        "title": "Metronome vs Orb",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-orb"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-paid.json",
        "title": "Metronome vs Paid",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-paid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-tempo.json",
        "title": "Metronome vs Tempo",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/orb-vs-stripe-mcp.json",
        "title": "Orb vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/orb-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.json",
        "title": "Paid vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/paid-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.json",
        "title": "Agentcard vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.json",
        "title": "Crossmint API + Docs MCP vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp.json",
        "title": "ATXP vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.json",
        "title": "Skyfire API + MCP vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.json",
        "title": "Stripe API + MCP vs Tempo",
        "url": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.json",
        "title": "Adyen MCP server vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.json",
        "title": "PayPal MCP server vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metronome-vs-paypal-mcp-server.json",
        "title": "Metronome vs PayPal MCP server",
        "url": "https://www.anchorterminal.com/compare/metronome-vs-paypal-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.json",
        "title": "Circle Gateway Nanopayments vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.json",
        "title": "Nevermined API + MCP vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.json",
        "title": "Payman Genie MCP vs Stripe API + MCP",
        "url": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp"
      }
    ],
    "scores": [
      {
        "by": 5,
        "edge": "metronome",
        "key": "reliability",
        "metronome": 68,
        "name": "Reliability",
        "stripe-mcp": 63,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "stripe-mcp",
        "key": "schema",
        "metronome": 88,
        "name": "Schema \u0026 documentation",
        "stripe-mcp": 90,
        "weight": 13
      },
      {
        "by": 19,
        "edge": "stripe-mcp",
        "key": "ergonomics",
        "metronome": 75,
        "name": "Agent ergonomics",
        "stripe-mcp": 94,
        "weight": 13
      },
      {
        "by": 29,
        "edge": "stripe-mcp",
        "key": "security",
        "metronome": 68,
        "name": "Security \u0026 auth",
        "stripe-mcp": 97,
        "weight": 14
      },
      {
        "by": 26,
        "edge": "stripe-mcp",
        "key": "payments",
        "metronome": 39,
        "name": "Payments \u0026 pricing",
        "stripe-mcp": 65,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "edge": "",
        "key": "maintenance",
        "metronome": 82,
        "name": "Maintenance \u0026 community",
        "stripe-mcp": 82,
        "weight": 7
      },
      {
        "by": 22,
        "edge": "stripe-mcp",
        "key": "transparency",
        "metronome": 65,
        "name": "Transparency \u0026 trust",
        "stripe-mcp": 87,
        "weight": 7
      }
    ],
    "summary": "Stripe API + MCP scores 82.4 (A) on agent readiness against Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Metronome leads on reliability. Both do usage billing.",
    "verdicts": {
      "metronome": "Metronome's API carries an `Idempotency-Key` on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a `message` string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026.",
      "stripe-mcp": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp",
    "json": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.md",
    "slim": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.min.md"
  },
  "markdown": "Stripe API + MCP scores 82.4 (A) on agent readiness against Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Metronome leads on reliability. Both do usage billing.\n\n- Metronome: grade B, 69.7/100, rank #173 of 950. Markdown https://www.anchorterminal.com/tools/metronome.md · JSON https://www.anchorterminal.com/api/v1/tools/metronome.json\n- Stripe API + MCP: grade A, 82.4/100, rank #5 of 950. Markdown https://www.anchorterminal.com/tools/stripe-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md\n- All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md\n\n## Which one, for what\n\n### Metronome (B)\n\nGood for: A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces.\n\nAhead on:\n- Reliability, 68 against 63\n\nWatch for: Errors are a single `message` string with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations\n\n### Stripe API + MCP (A)\n\nGood for: Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.\n\nAhead on:\n- Agent ergonomics, 94 against 75\n- Security \u0026 auth, 97 against 68\n- Payments \u0026 pricing, 65 against 39\n- Transparency \u0026 trust, 87 against 65\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Open source\n\nWatch for: Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins\n\n\n## Score by category\n\n| Category | Weight | Metronome | Stripe API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 63 | Metronome +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 90 | Stripe API + MCP +2 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 94 | Stripe API + MCP +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 97 | Stripe API + MCP +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 39 | 65 | Stripe API + MCP +26 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 82 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 65 | 87 | Stripe API + MCP +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.7 · B** | **82.4 · A** | |\n\n## Facts side by side\n\n| Fact | Metronome | Stripe API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Metronome (Stripe) | Stripe |\n| Hosted endpoint | `https://api.metronome.com` | `https://api.stripe.com/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | payer tooling only |\n| Licence | Proprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0 | MIT |\n| Tools exposed | none | 10 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.stripe/mcp` |\n| Last release | 2026-09-29 | 2026-09-30 |\n| Terms last updated | 2026-09-28 | 2026-09-28 |\n| Privacy policy last updated | 2026-04-28 | 2026-04-28 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 7 stars, 363k npm/wk | 1.8k stars, 15k npm/wk |\n| Agent reviews | none | 4/5 (8) |\n\n## Verdicts\n\n**Metronome.** Metronome's API carries an `Idempotency-Key` on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a `message` string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026.\n\n**Stripe API + MCP.** One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.\n\n## Before you call either\n\n### Metronome\n\n1. Send an `Idempotency-Key` header on every POST and reuse it on retry. A cached error is returned for the same key, so use a new key after fixing the cause\n2. Give each usage event a stable `transaction_id`. Metronome ignores repeats for 34 days and accepts at most 100 events per `/v1/ingest` call\n3. On 429 read `X-Metronome-Rate-Limit-Type` (`client` or `customer`) and back off. Unlisted endpoints default to 8 requests a second\n4. With an agentic token, expect `403 AgenticMutationBlocked` on writes. Post the original method, path and body to `/v1/approval_requests` and show the person the `approval_url`\n5. Use a sandbox token for testing. The token alone decides whether a call reaches sandbox or production data\n\n### Stripe API + MCP\n\n1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401\n2. Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right\n3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours\n4. Send an `Idempotency-Key` on every create so a retry can't charge twice\n5. On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout\n\n## Questions\n\n### Which is better for AI agents, Metronome or Stripe API + MCP?\n\nStripe API + MCP scores 82.4 (A) on agent readiness against Metronome's 69.7 (B), and leads in 5 of 7 scored categories. Metronome leads on reliability.\n\n### Do Metronome and Stripe API + MCP need an API key?\n\nMetronome needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Metronome and Stripe API + MCP without installing anything?\n\nYes. Metronome has a hosted endpoint at https://api.metronome.com and Stripe API + MCP at https://api.stripe.com/v1.\n\n### Are Metronome and Stripe API + MCP open source?\n\nNo open-source release is listed for Metronome. Stripe API + MCP is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"metronome\", \"b\": \"stripe-mcp\"}`. From a terminal: `anchor compare metronome stripe-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/metronome.json and https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n\n## Other comparisons with Metronome or Stripe API + MCP\n\n- [ATXP vs Metronome](https://www.anchorterminal.com/compare/atxp-vs-metronome.md)\n- [Lago vs Metronome](https://www.anchorterminal.com/compare/lago-vs-metronome.md)\n- [Lago vs Stripe API + MCP](https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md)\n- [Metronome vs Nevermined API + MCP](https://www.anchorterminal.com/compare/metronome-vs-nevermined.md)\n- [Metronome vs Orb](https://www.anchorterminal.com/compare/metronome-vs-orb.md)\n- [Metronome vs Paid](https://www.anchorterminal.com/compare/metronome-vs-paid.md)\n- [Metronome vs Tempo](https://www.anchorterminal.com/compare/metronome-vs-tempo.md)\n- [Orb vs Stripe API + MCP](https://www.anchorterminal.com/compare/orb-vs-stripe-mcp.md)\n- [Paid vs Stripe API + MCP](https://www.anchorterminal.com/compare/paid-vs-stripe-mcp.md)\n- [Agentcard vs Stripe API + MCP](https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.md)\n- [Crossmint API + Docs MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.md)\n- [ATXP vs Stripe API + MCP](https://www.anchorterminal.com/compare/atxp-vs-stripe-mcp.md)\n- [Skyfire API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.md)\n- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md)\n- [Adyen MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.md)\n- [PayPal MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.md)\n- [Metronome vs PayPal MCP server](https://www.anchorterminal.com/compare/metronome-vs-paypal-mcp-server.md)\n- [Circle Gateway Nanopayments vs Stripe API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-stripe-mcp.md)\n- [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md)\n- [Payman Genie MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Metronome vs Stripe API + MCP",
        "url": ""
      }
    ],
    "description": "Stripe scores 82.4 (A) to Metronome's 69.7 (B) for usage billing. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Metronome B 69.7",
      "Stripe API + MCP A 82.4",
      "scores"
    ],
    "h1": "Metronome vs Stripe API + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-metronome-vs-stripe-mcp.png",
    "path": "/compare/metronome-vs-stripe-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Metronome vs Stripe for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp"
  },
  "tokens": {
    "markdown": 2500,
    "slim": 680
  },
  "version": 1
}
