Paid vs Payman Genie 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.

Payman Genie MCP

OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.

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

Payman Genie MCP

1. Pass the person's request to ask_genie in their own words; don't pick accounts or fill payment fields
2. On needs_approval, stop and tell the person; approval happens in their Genie account
3. Retry only after NOTHING_RAN or BUSY, never after OUTCOME_UNKNOWN
4. Treat done as acted, not settled; check the activity history before confirming a payment
5. Sign-ins from bridge 0.3.x lack genie:self; log out and sign in again to use the self-service tools