Skip to content

feat(ecosystem): add CryptoAPIs facilitator - #264

Open
malin-globalinfratech wants to merge 1 commit into
coinbase:mainfrom
malin-globalinfratech:add-cryptoapis-facilitator
Open

feat(ecosystem): add CryptoAPIs facilitator#264
malin-globalinfratech wants to merge 1 commit into
coinbase:mainfrom
malin-globalinfratech:add-cryptoapis-facilitator

Conversation

@malin-globalinfratech

Copy link
Copy Markdown

Adds CryptoAPIs to the ecosystem as a Facilitator.

Two files:

  • typescript/site/public/logos/cryptoapis.png — 300×300, transparent
  • typescript/site/app/ecosystem/partners-data/crypto-apis/metadata.json

About

Non-custodial x402 facilitator settling USDC on Base and Solana (mainnet + testnet). Buyers sign payment authorizations locally with their own keys — CryptoAPIs never holds buyer keys and exposes no signing endpoint. The facilitator's wallets pay gas and submit settlement.

Verifiable without a credential

curl https://ai.cryptoapis.io/x402/merchant/supported
curl https://ai.cryptoapis.io/x402/merchant/discovery/resources

/supported returns the served kinds, the implemented extensions (payment-identifier) and signer addresses keyed by CAIP-2 namespace pattern. /verify and /settle require a merchant API key and answer with the spec's §9 standard error codes.

The declared networks mirror /supported exactly — the four with an enabled USDC asset — rather than every family the implementation supports, so the listing never advertises a chain /verify would reject.

Docs: https://developers.cryptoapis.io/v-2.2024-12-12-175/RESTapis/x402/x402-overview

@cb-heimdall

cb-heimdall commented Jul 29, 2026

Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

Non-custodial x402 facilitator settling USDC on Base and Solana, mainnet
and testnet.

Endpoints are live and publicly verifiable without a credential:
  GET https://ai.cryptoapis.io/x402/merchant/supported
  GET https://ai.cryptoapis.io/x402/merchant/discovery/resources

/supported advertises the served kinds, the implemented extensions
(payment-identifier) and the signer addresses keyed by CAIP-2 namespace
pattern; /verify and /settle require a merchant API key and answer with
the spec's standard error codes.

The declared networks mirror /supported exactly — the four with an enabled
USDC asset — rather than every family the implementation supports, so the
listing never promises a chain /verify would reject.
@malin-globalinfratech
malin-globalinfratech force-pushed the add-cryptoapis-facilitator branch from 85d3277 to 0ff0a7f Compare July 30, 2026 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants