Head to head · Card payments · October 2026 research run

Payman Genie MCP vs Skyfire API + MCP

Payman Genie MCP scores 47.1 (D) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in 4 of 7 scored categories. Skyfire API + MCP leads on schema & documentation, payments & pricing and transparency & trust. Both do card payments.

Best payment and monetisation platforms for AI agents · All 104 platforms comparisons

Which one, for what

Payman Genie MCP D

Best for A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.

Ahead on

  • Reliability, 25 against 19
  • Agent ergonomics, 68 against 61
  • Security & auth, 80 against 49
  • Maintenance & community, 30 against 4

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

No published pricing, status page, rate limits or changelog

Skyfire API + MCP E

Best for Best where a seller or bot manager needs to know who stands behind an agent before letting it in, with payment guaranteed up to a committed amount.

Ahead on

  • Schema & documentation, 69 against 56
  • Payments & pricing, 45 against 34
  • Transparency & trust, 55 against 46

Also in its favour

  • No incidents deducted, where Payman Genie MCP loses 3 points for them

Watch for

No x402 or MPP; both buyer and seller must be on Skyfire

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Payman Genie MCP +31

Payman Genie MCP 80

OAuth 2.1 with S256 PKCE, scopes genie:ask and genie:self, one-hour access tokens, refresh tokens rotated on every use and revoked through RFC 7009 on logout. Dynamic client registration is now documented (30). The owner sets per-payment, daily and monthly limits and approved payees, payments over an ask-me threshold need a six-digit code or passkey, and approvals happen in Genie, never in the chat. The assistant can grant itself read access only, and full access needs the owner (20). The agent passes the person's words to another agent; limits and out-of-band approval sit behind it, but we found no prompt-injection guidance as such (10). Genie says every decision is logged in an activity history (12). "AICPA SOC 2 certified" on the site and a Vanta trust centre we couldn't render, no security.txt per the 30 September check, and no disclosure policy or bug bounty found (8). No advisory for @paymanai/genie-mcp-stdio or any Payman package on osv.dev on 4 November. Genie holds no funds; money stays at the bank, card wallet or Coinbase, and we found no licence claim. The developer page, home page and trust centre readings are per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms). 30+20+10+12+8 = 80.

Skyfire API + MCP 49

A skyfire-api-key header, with separate buyer, seller and organisation admin key types so a buyer key can't charge and a seller key can't mint. Organisation admins can now create, list, deactivate and reactivate agent API keys through the API, and the docs give a rotation order (create the replacement, migrate, deactivate the old key; page updated 19 October), so scoped, revocable keys with rotation (30). A pay token caps what a seller can charge at its amount, expires in 10 seconds to 24 hours and is bound to one seller, and agents can be limited to set source IP addresses, but we found no buyer-side spending cap on an agent and no confirmation on create-pay-token (10). find-sellers returns third-party listings with no prompt-injection guidance (6). No audit log found (0). Tokens are JWTs verified against a public JWKS, with jti for replay checks, and Skyfire runs KYB on buyer platforms and KYC through Persona. security.txt answers 404 on 10 November and no disclosure policy, bug bounty or SOC 2 was found (3). 30 + 10 + 6 + 0 + 3 = 49. Funds sit in "a digital wallet set up by Skyfire or our service providers", the terms name no bank, custodian or licence, and credits are non-refundable.

Maintenance & community Payman Genie MCP +26

Payman Genie MCP 30

The bridge's newest tagged release is v0.2.1 (14 September 2026), 51 days before 4 November (20). Since 6 August the repository has two tagged releases, v0.2.0 and v0.2.1, both on 14 September; the 0.3.0 and 0.4.0 version bumps of 18 September carry no tag or changelog entry, so they don't count as releases, and no commit has landed since 18 September (0). Two merged pull requests and no changelog. The older developer platform looks abandoned, with docs.paymanai.com failing on a Cloudflare 526 and the payman-ts SDK last released on 18 September 2025, per the 1 October check, not re-read on 4 November (5). No current SDK, and the official MCP registry wasn't read first-hand (0). A Node test suite with a fake authorisation server, but no CI workflow in the repository (5). 20+0+5+0+5 = 30.

Skyfire API + MCP 4

No changelog and no dated API change found; reference page update stamps record no change, and the 4 August 2026 date of seller SDK 0.0.7 came from the npm registry document, which this check doesn't use (it would be 98 days old, 10, either way) (0). No release or dated change in the 90 days from 12 August (0). No changelog and no public SDK repository; the KYAPay specification repository's newest commit is a dependency pin on 2 September, and support is by email (4). No official SDK named in the docs, and the npm reading is struck (0). No package or CI we could read (0). 0 + 0 + 4 + 0 + 0 = 4.

Schema & documentation Skyfire API + MCP +13

Payman Genie MCP 56

Five MCP tools, but the server is closed and ask_genie takes a free-text request by design, so the contract is thin (15 of 25). No llms.txt; the bridge README has a Markdown "For agents" section (3). The developer page states what each status means and what the caller should do next, including to stop on needs_approval and not to rephrase after refused (16). One free-text field plus optional context and conversation, no enums (6). Five statuses and three retry codes documented with the action for each (13). No changelog or versioning beyond the bridge's git history (3). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026).

Skyfire API + MCP 69

Each API reference page's Markdown version carries an OpenAPI 3.1.0 fragment for its operation (spec "skyfire-agent-and-token-apis" 1.0, server https://api.skyfire.xyz), with no single file to download; per-page fragments take 20, as lucid and chroma did (20). llms.txt with 91 entries, 46 of them API reference pages, each served as Markdown (10). The docs explain when to use a kya, pay or kya-pay token and when to name an onboarded or an external seller, while the MCP tool descriptions are one line each (12). Token type is one of three values, expiresAt is clamped to 10 seconds to 24 hours, amounts are plain decimal strings with stated precision, and sellerServiceId and sellerDomainOrUrl are mutually exclusive (11). Ten error codes documented with a fixed code, message, details body and handling advice (12). /api/v1 in paths and no changelog (4). 20 + 10 + 12 + 11 + 12 + 4 = 69.

Payments & pricing Skyfire API + MCP +11

Payman Genie MCP 34

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Genie pays x402 APIs from a daily agent budget the owner sets, the buyer step (15 of 40). Payman has no way to accept x402 or MPP, and Genie itself isn't paid over either. No price list for Genie anywhere we looked (0). Free signup with no card or bank details (20). A person signs up and signs in through a browser (0). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 20 is 30 at 30 each, so 35 is 34.

Skyfire API + MCP 45

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. No x402, MPP or L402 in the docs index or the pages read on 10 November. Payment runs on Skyfire's own KYAPay tokens, an open specification but none of the three protocols, so the own-protocol step (0). No price list; the terms (25 June 2025) say Skyfire doesn't currently charge for buying credits or generating tokens and may add fees with 30 days' notice (10). The quickstart signs a person up by email magic link and creates a buyer agent with a pre-funded wallet, with no card step (20). A person signs up in the dashboard, and paid services need identity checks, before an agent can pay; the organisation APIs that mint users and keys need an admin who signed up first (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust Skyfire API + MCP +9

Payman Genie MCP 46

Bridge under MIT, Genie closed under published terms (updated 1 November 2026) and an API licence (15). Privacy policy updated 21 September 2026 names Payman AI, Inc. in Durango, Colorado, gives no retention periods and no DPA, and says anonymised or aggregated data is used to train AI models (12). No deprecation notice for the old developer platform even though its docs no longer load (0). Stripe, Google and unnamed identity-verification and credit-bureau providers are named, with transfers "including the United States" (6). The privacy policy is per the 1 October check, not re-read on 4 November. 15+12+0+6 = 33.

Skyfire API + MCP 55

Closed service under terms dated 25 June 2025, re-read on 10 November. The KYAPay specification is published under the Community Specification License with its example code under MIT (17). Privacy policy dated 25 June 2025, unchanged, links a DPA, names Persona and Google Analytics, keeps data in US data centres, gives no retention periods, permits training AI models on personal data, and says sellers receive any personal information carried in a token (18). No deprecation policy or notices found (0). A service-providers page lists processors, and data locations are stated (15). 17 + 18 + 0 + 15 = 50.

Agent ergonomics Payman Genie MCP +7

Payman Genie MCP 68

One money tool and four small self-service tools (get_genie_agent, rename_genie_agent, grant_genie_read_access, request_genie_access) (25). Answers are natural-language messages with no size or filter controls (5). The status field (done, needs_input, needs_approval, refused, error) tells the agent what to do next (18). Retry rules separate safe and unsafe failures, and done is documented as not proof of settlement. We couldn't check tool annotations (12). One required parameter, but no SDK; Genie is MCP only, plus the stdio bridge (8). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026).

Skyfire API + MCP 61

Four compact MCP tools, create-kya-token, create-pay-token, create-kya-payment-token and find-sellers (25). find-sellers takes a search term, and we found no page-size or field controls (8). Ten stable error codes with field-level details on validation errors and advice on which answers not to retry (16). No idempotency key on token creation; a CONFLICT answer creates nothing, and sellers dedupe on the token's jti (6). Token creation needs only type and a seller, with the expiry and funding wallet defaulted; the earlier reading of a Node seller SDK came from the npm registry document, which this check doesn't use, and no SDK is named in the docs (6). 25 + 8 + 16 + 6 + 6 = 61.

Score by category

CategoryWeightPayman Genie MCPSkyfire API + MCPEdge
Reliability16%2519Payman Genie MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5669Skyfire API + MCP +13
Agent ergonomics13%6861Payman Genie MCP +7
Security & auth14%8049Payman Genie MCP +31
Payments & pricing10%3445Skyfire API + MCP +11
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%304Payman Genie MCP +26
Transparency & trust7%4655Skyfire API + MCP +9
Negative events≤15-30
TotalD 47.1/100E 44.3/100

Facts side by side

FactPayman Genie MCPSkyfire API + MCP
KindHTTP APIHTTP API
VendorPayman AISkyfire
Hosted endpointhttps://genie.paymanai.com/mcphttps://api.skyfire.xyz
TransportsStreamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuthAPI key
PricingPaidFreemium
x402payer tooling onlyno
LicenceMITnone
Tools exposed54
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-192026-08-04
Terms last updated2026-09-292025-06-25
Privacy policy last updated2026-09-292025-06-25
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity0 stars, 33 npm/wknone
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Payman Genie MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

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.

Skyfire API + MCP

Identity and payment travel in one signed JWT that sellers verify offline against a public JWKS, and organisation admins can rotate and revoke agent keys through the API. There is no x402 or MPP, both buyer and seller must be on Skyfire, and no status page, changelog or dated release was found.

Before you call either

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

Skyfire API + MCP

  1. Buyer keys create tokens and seller keys charge them; a 403 usually means the wrong key type or a deactivated key
  2. Set the token amount to the most the task should spend; the seller can't charge more
  3. Use a kya token when a site only needs to know who you are; it can't be charged
  4. Don't retry 4xx answers unchanged; retry only a 500 SERVER_ERROR, with backoff
  5. Rehearse against mcp-sandbox.skyfire.xyz before using mcp.skyfire.xyz

Questions

Which is better for AI agents, Payman Genie MCP or Skyfire API + MCP?

Payman Genie MCP scores 47.1 (D) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in 4 of 7 scored categories. Skyfire API + MCP leads on schema & documentation, payments & pricing and transparency & trust.

Do Payman Genie MCP and Skyfire API + MCP need an API key?

Payman Genie MCP uses an OAuth sign-in. Skyfire API + MCP needs an API key.

Can an agent call Payman Genie MCP and Skyfire API + MCP without installing anything?

Yes. Payman Genie MCP has a hosted endpoint at https://genie.paymanai.com/mcp and Skyfire API + MCP at https://api.skyfire.xyz.

Other comparisons with Payman Genie MCP or Skyfire API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.