Stripe

stripe-rest-v1restprimary

98% coverage

Offload Valuejudged · weight 15 · Oct 5, 2026

Stripe performs real-world irreversible side effects an agent cannot simulate: moving funds, charging cards, payouts, transfers, refunds, subscriptions, tax rates, fraud/radar, identity and compliance. It also interacts with banking networks and card issuers, returning decline codes and network advice codes no amount of inference could produce. This is far beyond storage.

• https://docs.stripe.com/api

  You can use the Stripe API in sandboxes without affecting your live data or interacting with banking networks.

• https://docs.stripe.com/api

  You can use the Stripe API in sandboxes without affecting your live data or interacting with banking networks.

• https://docs.stripe.com/api

  You can use the Stripe API in sandboxes without affecting your live data or interacting with banking networks.

Interaction Costmeasured · weight 15 · Oct 5, 2026

Median over 2 successful run(s): 17720 tokens, 3.5 calls. Ratio to the best in "payments" (3 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Error Recoverabilityprobed · weight 15 · Oct 5, 2026

unknown_endpoint → HTTP 404, clarity 85/100 (field named: yes, allowed values: yes, RFC 9457: no) · wrong_type → HTTP 400, clarity 85/100 (field named: yes, allowed values: yes, RFC 9457: no) · hallucinated_enum → HTTP 400, clarity 85/100 (field named: yes, allowed values: yes, RFC 9457: no) · unknown_field → HTTP 400, clarity 85/100 (field named: yes, allowed values: yes, RFC 9457: no) · missing_required_param → HTTP 400, clarity 60/100 (field named: no, allowed values: yes, RFC 9457: no) · idempotency_replay → HTTP 200, clarity 30/100 (field named: no, allowed values: no, RFC 9457: no)

• https://api.stripe.com/v1/customers

  HTTP 401: { "error": { "message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https

• https://api.stripe.com/v1/customers/nonexistent_resource_xyz

  HTTP 404: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: 'nonexistent_resource_xyz'", "param": "id",

• https://api.stripe.com/v1/customers?limit=not_a_number

  HTTP 400: { "error": { "code": "parameter_invalid_integer", "doc_url": "https://stripe.com/docs/error-codes/parameter-invalid-integer", "message": "Invalid integer: not_a_number", "param": "li

• https://api.stripe.com/v1/customers?expand%5B%5D=nonexistent_relation

  HTTP 400: { "error": { "message": "This property cannot be expanded (nonexistent_relation). You may want to try expanding 'data.nonexistent_relation' instead.", "request_log_url": "https://dashboard.s

Doc Legibilitymeasured · weight 12 · Oct 5, 2026

text/markup ratio 0.7% (weight 30) · rendering without JavaScript undetermined (excluded from the calculation) (weight 25) · machine-readable spec: none found (weight 25) · llms.txt: https://docs.stripe.com/llms.txt (weight 10) · 2 runnable example(s) (weight 10). Weighted average over 75 points of available sub-criteria.

• https://docs.stripe.com/api
• https://docs.stripe.com/llms.txt

Auth Frictionmeasured · weight 10 · Oct 5, 2026

Authorization: Bearer <key>, verified by a successful call. One header, no ceremony.

• https://api.stripe.com/v1/customers

  HTTP 401: { "error": { "message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https

• https://api.stripe.com/v1/customers/nonexistent_resource_xyz

  HTTP 404: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: 'nonexistent_resource_xyz'", "param": "id",

• https://api.stripe.com/v1/customers?limit=not_a_number

  HTTP 400: { "error": { "code": "parameter_invalid_integer", "doc_url": "https://stripe.com/docs/error-codes/parameter-invalid-integer", "message": "Invalid integer: not_a_number", "param": "li

• https://api.stripe.com/v1/customers?expand%5B%5D=nonexistent_relation

  HTTP 400: { "error": { "message": "This property cannot be expanded (nonexistent_relation). You may want to try expanding 'data.nonexistent_relation' instead.", "request_log_url": "https://dashboard.s

Safety & Reversibilityprobed · weight 10 · Oct 5, 2026

Two identical POSTs with the same Idempotency-Key header return the same resource (cus_VNwfjOMrDryZg6). An agent can retry without risking a duplicate. (weight 35) · Isolated test environment available. (weight 25). Weighted average over 60 points of measured sub-criteria.

• https://api.stripe.com/v1/customers

  HTTP 401: { "error": { "message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https

• https://api.stripe.com/v1/customers/nonexistent_resource_xyz

  HTTP 404: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: 'nonexistent_resource_xyz'", "param": "id",

• https://api.stripe.com/v1/customers?limit=not_a_number

  HTTP 400: { "error": { "code": "parameter_invalid_integer", "doc_url": "https://stripe.com/docs/error-codes/parameter-invalid-integer", "message": "Invalid integer: not_a_number", "param": "li

• https://api.stripe.com/v1/customers?expand%5B%5D=nonexistent_relation

  HTTP 400: { "error": { "message": "This property cannot be expanded (nonexistent_relation). You may want to try expanding 'data.nonexistent_relation' instead.", "request_log_url": "https://dashboard.s

Payload Efficiencyprobed · weight 8 · Oct 5, 2026

No discoverable field selection (tested fields, select, _fields, expand, properties): the agent swallows the whole resource. (weight 35) · 527 bytes per returned object (7 object(s) in the control response). (weight 25) · Cursor pagination detected ("has_more"). (weight 20) · One list envelope, standard. (weight 10) · No ETag. (Compression is not measurable: the runtime decompresses it and strips the header.) (weight 10). Weighted average over 100 points of measured sub-criteria.

• https://api.stripe.com/v1/customers

  HTTP 401: { "error": { "message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https

• https://api.stripe.com/v1/customers/nonexistent_resource_xyz

  HTTP 404: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: 'nonexistent_resource_xyz'", "param": "id",

• https://api.stripe.com/v1/customers?limit=not_a_number

  HTTP 400: { "error": { "code": "parameter_invalid_integer", "doc_url": "https://stripe.com/docs/error-codes/parameter-invalid-integer", "message": "Invalid integer: not_a_number", "param": "li

• https://api.stripe.com/v1/customers?expand%5B%5D=nonexistent_relation

  HTTP 400: { "error": { "message": "This property cannot be expanded (nonexistent_relation). You may want to try expanding 'data.nonexistent_relation' instead.", "request_log_url": "https://dashboard.s

Task Atomicitymeasured · weight 6 · Oct 5, 2026

Median over 2 successful run(s): 17720 tokens, 3.5 calls. Ratio to the best in "payments" (3 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Prior Knowledge Coveragemeasured · weight 5 · Oct 5, 2026

Median over 2 successful run(s): 17720 tokens, 3.5 calls. Ratio to the best in "payments" (3 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Async Compatibilityprobed · weight 2 · Oct 5, 2026

POST /customers returns an identifier, and GET /customers/{id} reads it back (HTTP 200): the result can be retrieved by polling, with no server to host. Long-polling / SSE not probed, excluded from the weighting.

• https://api.stripe.com/v1/customers

  HTTP 401: { "error": { "message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https

• https://api.stripe.com/v1/customers/nonexistent_resource_xyz

  HTTP 404: { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: 'nonexistent_resource_xyz'", "param": "id",

• https://api.stripe.com/v1/customers?limit=not_a_number

  HTTP 400: { "error": { "code": "parameter_invalid_integer", "doc_url": "https://stripe.com/docs/error-codes/parameter-invalid-integer", "message": "Invalid integer: not_a_number", "param": "li

• https://api.stripe.com/v1/customers?expand%5B%5D=nonexistent_relation

  HTTP 400: { "error": { "message": "This property cannot be expanded (nonexistent_relation). You may want to try expanding 'data.nonexistent_relation' instead.", "request_log_url": "https://dashboard.s

Tool-Native (MCP)binary · weight 2

Does the vendor publish an official, maintained MCP server?