Sell your AI, compute, or data API across borders.
For upstream providers — model APIs, GPU and inference time, data processing — who want to serve overseas customers without first opening a foreign bank account, onboarding to a card processor, or building a full SaaS account product.
Without xpayapi
Foreign bank account, payment-processor entity & KYC, FX conversion, batched payouts, per-customer invoicing
With xpayapi
Wallet settlement in USDC, no foreign entity required for the payment leg, provider-hosted traffic
Who this is for
-
Model & token providers
Fine-tuned models, inference endpoints, OpenAI-compatible APIs. Per-token pricing maps naturally to per-call settlement; overseas developers and agents can call you without you running a billing account product for them.
-
GPU & compute providers
Inference time, embedding workers, image and video generation, batch jobs. Charge per call, per second, or per task without a card processor in the middle.
-
Data processing & cross-border data services
OCR, transcription, translation, enrichment, web data, vertical datasets. Overseas customers can call your endpoint and pay per request, with what they sent and what you returned staying on your infrastructure.
What you get
-
Settlement without a foreign bank stack
Customers pay in USDC, a fiat-backed stablecoin. Funds settle wallet-to-wallet — no foreign bank account, payment-processor entity, or FX conversion in the receiving path.
Evidence: USDC transfers are public on-chain transactions to the wallet address you configure; your finance team can reconcile against any chain explorer.
-
Small-unit settlement fits API usage
Fractional-cent and sub-cent usage models fit the protocol directly. Providers can configure per-call, per-task, or usage-based routes without relying on card-style minimum charges.
Evidence: the proxy verifies payment per request and returns a receipt, so each paid call has an auditable payment record.
-
Overseas discovery without an English marketing funnel
Your API is listed alongside others in an English-language directory. Wallet-holding callers and agents browse by category and endpoint; the docs profile is generated from the metadata your proxy ships.
Evidence: callers see your category, OpenAPI paths, request schemas, and examples before making a request.
-
You stay in control of data and infra
Caller traffic goes to your provider-hosted proxy and upstream API. xpayapi receives listing metadata for discovery and docs, not API request or response payloads. You decide where the proxy runs and where the upstream is deployed.
Evidence: the public base URL points to infrastructure you operate; payment settles to the wallet address you set.
Evidence behind the claims
Cross-border payment economics are public. These are the mechanics you can verify before publishing.
Card fee math
Card fees price out per-token AI calls
Stripe’s public US card pricing lists 2.9% + $0.30 per successful charge. A $0.30 fixed fee is 300% of a $0.10 call before the percentage fee, and international cards add further cross-border and currency fees. Per-call stablecoin settlement removes the minimum-fee floor.
Wire economics
Wires aren’t a per-call rail
International bank wires typically carry sender and intermediary fees and take one or more business days to land. Per-call API usage is not a workload wires are priced for. On-chain transfers settle in seconds at a fixed protocol cost.
Data boundary
Discovery metadata is separate from API traffic
The directory needs listing metadata such as OpenAPI paths, categories, and examples. The caller’s request body and your response stay on the provider-hosted API path.
Scope: xpayapi is an API directory — it lists your service for discovery and builds a public docs profile from the metadata you publish. Per-call payment and wallet settlement are handled by the open-source proxy you run; xpayapi is not in the payment path. It is not a cross-border compliance service. Data-export rules, AI export controls, sanctions screening, customer-side KYC, content licensing, and local tax obligations remain entirely your responsibility.
Common cross-border questions
- Can a non-US entity receive payments?
- Settlement is a wallet-to-wallet USDC transfer; no US bank account or US entity is required for the payment leg. Whether you can legally hold, convert, or report USDC depends on your jurisdiction — confirm with local counsel before going live.
- How do I cash USDC out to a local bank?
- Off-platform. Typically through a centralized exchange or OTC desk available in your jurisdiction. xpayapi does not custody funds or handle cash-out; understand your spread and timeline before you price routes.
- What about my country’s data-export or AI-export rules?
- xpayapi is a directory platform, not a compliance partner or regulator. You remain responsible for whether you can legally serve foreign customers — data residency, AI-model or compute export controls, content moderation, and content licensing all apply as before.
- Can I block specific customers, wallets, or regions?
- Yes. The proxy can require an additional auth header, allowlist specific wallets, or reject regions before forwarding the request to your upstream. Treat the payment proof as one input to your access decision, not the whole policy.
- Does xpayapi take a cut?
- xpayapi is not in the payment path; settlement goes directly to the wallet you configure. Directory listing is free during preview; any future platform fee should be disclosed before it applies.
- What about latency for overseas customers?
- The proxy adds one verification step before forwarding; the upstream call runs on your infrastructure. If your customers are concentrated in a specific region, deploy the proxy and upstream where they need it — the architecture does not pin you to any region.
- Am I exposed to crypto price volatility?
- USDC is a fiat-backed stablecoin pegged to the US dollar; on the receivables side you are holding a dollar-denominated balance, not a speculative token. Treat conversion timing as a normal FX decision.