Bridge
Stablecoin payments infrastructure (acquired by Stripe) offering an orchestration, issuance, cards, and wallet API for moving money onchain.
- Sato Score40
- ChainsMultichain
Bridge is a closed-source payment rail, with no code activity tracked. Sato Score 40/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install Bridge →No code activity tracked
Listed from bridge.xyz on 2026-07-19. Install: not attempted. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about Bridge before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Bridge provides a single API for stablecoin orchestration (move/store/accept stablecoins), stablecoin issuance backed by US Treasuries, card programs via Stripe Issuing, and programmatic wallet creation. An agent builder uses its API to move funds cross-border or issue payouts without building settlement and compliance infrastructure from scratch.
Sato Score
40/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 0/20
- Interface verifiability
- 0/10
- Docs & demo
- 10/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from bridge.xyz on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | apidocs.bridge.xyz | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | bridge.xyz | as of 2026-10-21 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | apidocs.bridge.xyz | as of 2026-09-14 |
| Website answers | answered (HTTP 200) | observed | bridge.xyz | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Demo available | yesconfidence 0.90 | self-reported | apidocs.bridge.xyz | as of 2026-09-19 |
| Sato Score | 40/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: REST API (any HTTP client; no SDK install documented)
curl --location --request POST 'https://api.bridge.xyz/v0/transfers' --header 'Api-Key: <API Key>' --header 'Idempotency-Key: <Unique Idempotency Key>' --data-raw '{"on_behalf_of": "cust_alice", "source": {"payment_rail": "ach_push", "currency": "usd"}, "destination": {"payment_rail": "ethereum", "currency": "usdc", "to_address": "0xdeadbeef"}, "features": {"flexible_amount": true}}'
POST https://api.bridge.xyz/v0/transfersYou supply: Api-Key header (Bridge-issued API key), Idempotency-Key header (unique per request)
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- Stablecoin payments API
- Open source
- No
- Last checked
- 2026-10-21
Marketplace Signals
- ▸ Demo available
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Listing History
Recorded changes to Bridge's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 26, 2026Edited: entity class, resource type
- Sep 19, 2026Auto-enriched: has demo
- Sep 19, 2026Sato Score tier: Low → MediumScore 35 → 40.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Listed on Sato Hub
Compared with
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
x402
EarlyOpen HTTP 402 payment protocol, now at the x402 Foundation: agents pay per request in stablecoins, and by a newly merged spec, in bitcoin over Lightning.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Bridge
- Is Bridge open source?
- No. Bridge is closed source as of 2026-10-21.
- Which chains does Bridge support?
- Bridge lists support for Multichain as of 2026-10-21.
- Is Bridge still maintained?
- Sato Hub tracks no commit or release for Bridge; it cannot say whether it is maintained.
- How do I install or run Bridge?
- REST API (any HTTP client; no SDK install documented). Install: curl --location --request POST 'https://api.bridge.xyz/v0/transfers' --header 'Api-Key: <API Key>' --header 'Idempotency-Key: <Unique Idempotency Key>' --data-raw '{"on_behalf_of": "cust_alice", "source": {"payment_rail": "ach_push", "currency": "usd"}, "destination": {"payment_rail": "ethereum", "currency": "usdc", "to_address": "0xdeadbeef"}, "features": {"flexible_amount": true}}'. Entry: POST https://api.bridge.xyz/v0/transfers. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is Bridge verified on Sato Hub?
- No independent verification is on record for Bridge; its verification status is "Unverified" and its Sato Score is 40 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Bridge — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/bridge-xyzData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.