Payment rails beyond Stripe — native USDC on Base, MPP and XRPL endpoints exist but are newer and far less battle-tested. XRPL runs on testnet only and its real-network settlement is not yet confirmed. Stripe is the path we recommend for production.
Enterprise SSO is a first implementation, tested against real attack patterns — but authentication infrastructure deserves an external security review before you rely on it for sensitive access, not just our own testing.
Pricing FAQ
No. run.pay charges 2% per call — that's it. No monthly fee, no setup fee, no minimum spend. If your agent makes 0 calls this month, you pay $0.
You can set up automatic refills — when your balance drops below a threshold, Stripe charges your card to top it up. If refill fails, the API call returns a 402 error so your agent can handle it gracefully.
Yes. If a service returns a 5xx error, the call is not charged. You only pay for successful responses (2xx).
Vendors receive 98% of each call via Stripe Connect, paid out weekly directly to their bank account. No invoicing. Balances under $1 simply roll over to the next payout.
In the Playground, every service can be tried 3 times free, with no credit card. To call services from your own code, fund a wallet and pay per call.
Because the real gap isn't features — it's whether you're managing one agent's spend or an organization's. That's a different problem, not a bigger version of the same one.
No — publishing to the public marketplace is available on the free Vendor account. Enterprise is for centralizing control across multiple agents you run, not for selling.
Contact Sales — this is exactly the kind of conversation that tier exists for.
Contact Sales
Tell us about your organization — we'll get back to you shortly.