Paid vs Stripe API + MCP

Paid

Paid suits a builder who wants usage metering, credits and invoicing behind one API, with restricted and customer-bound keys, OAuth on the MCP server and a free plan that needs no card. No status page, SLA figure, API changelog or rate-limit numbers were found, both advertised OpenAPI links returned 404, and card payments need the builder's own Stripe account.

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.

Paid

1. Call https://api.agentpaid.io/api/v2 with Authorization: Bearer <key>. A person creates the first key at app.paid.ai. No programmatic signup was found
2. Give every signal a stable idempotencyKey and resend the same key on retry. Signals without one are not deduplicated
3. Send at most 500 signals a request. A 429 rejects the whole batch, so wait for Retry-After and resend it all
4. Read the code field on a 429. CONCURRENCY_LIMIT_EXCEEDED carries no Retry-After and clears when an analytics query finishes
5. Install the Python SDK as paid-python, the name in its README and pyproject.toml. The quickstart's pip install paid names a package we could not check

Stripe API + MCP

1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401
2. Call stripe_api_search and stripe_api_details before stripe_api_write to get the method and parameters right
3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours
4. Send an Idempotency-Key on every create so a retry can't charge twice
5. On 429, read Stripe-Rate-Limited-Reason and back off with jitter; a 429 without it is a lock timeout