Product ▾ Solutions ▾ Developers Pricing

Solutions

Wherever agents transact, someone carries the risk

The agent economy is being built by platforms — commerce, paid services, marketplaces, procurement suites, assistants, and the infrastructure underneath them all. Six use cases, one trust layer: Nustro moves the liability off your books and onto a system built to hold it.

Contact sales Start in sandbox

Find your use case in one sentence

My merchants sell to shopping agentsAgentic commerce →My vendors sell services per callMachine-native services →Agents transact on my platformAgent marketplaces →My customers’ agents close dealsAutonomous procurement →My assistant buys for my usersConsumer agents →I host or route others’ agentsAgent infrastructure →

Many platforms are two of these at once — a travel platform with agent checkout and its own assistant is both. Each use case stands alone.

Agentic commerce Machine-native services Agent marketplaces Autonomous procurement Consumer agents Agent infrastructure Why Nustro

Use case 01 · Agentic commerce

Give your merchants agent checkout that answers for itself

You run the commerce platform — your merchants sell to shopping agents.

Checkout standards let AI shopping agents buy across your merchants at scale. What none of them carries is accountability: who the buying agent is, whether its owner authorized the purchase, and who answers when an order is wrong. Today, that lands on you and your merchants.

Today

✕Shopping agents arrive with no verifiable identity — neither you nor your merchants can tell a customer’s agent from a fraudster’s.

✕Liability for a purchase the customer never intended is negotiated deal by deal; no standard protects your merchants.

✕Commerce protocols orchestrate the checkout — none of them answers for the outcome.

With Nustro

✓Gate agent checkout across every storefront on a verified certificate — proof of who the agent is and who stands behind it.

✓Wrong or failed orders resolve as disputes with defined windows, paid from escrow — recourse you offer as a platform feature.

✓Complementary by design: checkout stays on the rails you adopted; Nustro carries the accountability those rails don’t.

commerce platform · agent checkout

shopping agentpays → ordermerchant storefront

merchant storefrontfulfils ← proofshopping agent

shopping agent⚖ dispute · wrong itemmerchant storefront

Integration sketch

1Onboard each merchant as a principal; register their storefront agents — DID, signed AID, certificate.

2Verify inbound buying agents’ certificate and agent_rating before accepting an order.

3Settle through Nustro so escrow accrues against each storefront agent per transaction.

4Wire dispute.filed / dispute.resolved into your order-management flow.

campaign · one orchestrator, many services

campaign agentpays → per callcopywriting service

campaign agentpays → per callad-placement service

ad-placement servicedelivers ← PoP accruescampaign agent

campaign agent⚖ dispute · bad outputad-placement service

Integration sketch

1Onboard vendors as principals; register one provider agent per endpoint.

2Surface certificate state and agent_rating in your catalog and discovery metadata, next to price.

3Settle through Nustro so escrow accrues against each endpoint per transaction.

4Wire dispute webhooks into your quality and delisting tooling.

Use case 02 · Machine-native services

Run the exchange where agents buy services per call

You run the platform where vendors sell APIs, data and tasks — agents pay per call.

Micropayments made charging agents trivial: respond 402, get paid, serve. Your vendors get paid — but an orchestrating agent assembling a marketing campaign is hiring six services it has never used, and in your catalog, price is the only signal any of them show.

Today

✕A paid call that returns garbage is money gone — at micro scale, recourse is “not worth it” individually and material in aggregate.

✕No track record attaches to the endpoints in your catalog — a first-rate vendor and a fly-by-night one quote the same way.

✕Buying agents throttle spend on unknown vendors — quality on your platform cannot earn volume.

With Nustro

✓Every listed endpoint carries a certificate and a settlement-derived rating — quality becomes provable, in your catalog.

✓Vendor escrow scaled to volume backs every call; buyers price the risk of trying someone new at zero.

✓Your payment rails stay: they move the money, Nustro answers for what it bought.

Use case 03 · Agent marketplaces

Run the marketplace where agents hire agents

You run the venue — third-party agents transact on your platform.

Platforms where autonomous agents post work, bid, and get paid are live today — and each one is improvising its own escrow, its own ratings, its own dispute handling. That improvisation is your liability and your ceiling.

Today

✕Escrow is rebuilt per platform, held by the platform, trusted on faith.

✕Ratings are platform-local and gameable — an agent’s record dies at your boundary.

✕A failed job becomes your support queue and, usually, your refund.

With Nustro

✓Every listed agent carries a certificate, protocol escrow in its own wallet, and a rating derived from settlements.

✓Reputation is a protocol object — verifiable by anyone, credible beyond your walls, and a reason to list with you.

✓Disputes are decided against the provider’s escrow. You list, Nustro underwrites.

marketplace · task lifecycle

hiring agentpays → tasklisted agent

listed agentdelivers ← PoP accrueshiring agent

hiring agent⚖ dispute · escrow holdlisted agent

Integration sketch

1Onboard the seller as a principal; register their agent — DID, signed AID, certificate.

2Show certificate state and agent_rating on the listing; both verifiable by anyone.

3Route task payments through settlement — escrow accrues automatically.

4Wire dispute webhooks into your job and payout flow.

cross-company · procurement

buyer co. agentverifies AIDsupplier co. agent

buyer co. agentpays → ordersupplier co. agent

supplier co. agentdelivers ← PoP accruesbuyer co. agent

Integration sketch

1Register each enterprise customer as a principal; their buying agents live under it.

2Verify supplier certificates and agent_rating before ordering — as suite policy, not per-deal diligence.

3Settlement splits escrow and fee on-chain; both sides audit every leg.

4Surface dispute filing and state inside your suite via dashboard or API.

Use case 04 · Autonomous procurement

Let buyer and supplier agents close deals alone

You build the procurement suite — your enterprise customers’ agents close deals.

You are shipping agents that evaluate suppliers, negotiate, and execute purchases for your enterprise customers. Bot-to-bot deal-making is on your roadmap — and it runs ahead of any answer to “what if the agent is wrong?” That answer is your differentiation.

Today

✕A customer’s agent that overpays, double-orders, or buys from a ghost has no recourse but a lawyer.

✕Counterparty diligence is manual and per-relationship — it cannot run at agent speed.

✕Authority is unprovable: nothing shows a supplier that your customer’s agent was empowered for this order.

With Nustro

✓Both agents present verifiable identity — capabilities, principal, dispute terms — before money moves.

✓The supplier’s escrow bounds your customers’ downside on every order, automatically.

✓Disputes resolve against escrow in days, in-protocol — a suite feature your competitors negotiate in contracts.

Use case 05 · Consumer agent platforms

Your assistant spends their money. Protect both of you.

You ship the assistant — your agents spend your users’ money.

Travel, dining, delivery, retail — assistants that book and buy for customers are shipping now. Every transaction is your brand on the line against counterparties you have never seen, and “the AI made a mistake” lands on you.

Today

✕Your agent pays an unknown provider; when nothing arrives, your customer blames you.

✕A purchase the customer never wanted is a goodwill refund and a churn risk.

✕You cannot tell your customer what recourse they have, because there isn’t one.

With Nustro

✓Your agents transact only with certified providers — identity and rating checked before they pay.

✓When a task fails, you file a dispute on the customer’s behalf; the remedy comes from the provider’s escrow, not your margin.

✓“Protected by Nustro” becomes a product feature you can print.

consumer product · assistant flow

customer’s agentchecks cert + ratingservice provider

customer’s agentpays → bookingservice provider

customer’s agent⚖ dispute if it failsservice provider

Integration sketch

1Register your assistant fleet as consumer agents — no escrow to fund; consumers carry no liability stack.

2Gate outbound payments on certificate state and minimum agent_rating.

3Surface the dispute window to your customer after each purchase.

4File disputes through the Platform on the agent’s behalf — relay-authenticated, no wallet keys involved.

fabric · policy-gated routing

hosted agentgateway verifies certpaid endpoint

hosted agentpays → invocationpaid endpoint

hosted agent⚖ dispute · bad responsepaid endpoint

Integration sketch

1Verify counterparty certificates at the gateway before routing — deny on revoked or missing.

2Enforce a minimum agent_rating as fabric policy, per tenant or per route.

3Pass agent auth headers through untouched — agents authenticate per request; your management key never reaches a runtime.

4Surface settlement and dispute state to tenants via webhooks.

Use case 06 · Agent infrastructure

Embed accountability where the traffic already flows

You host or route other people’s agents — runtimes, fabrics, gateways.

Runtimes host the agents. Integration fabrics route their calls. Monetization gateways meter what they consume. In AEA/P terms, that is the Platform role — the PSP of the agent economy: you route and enforce policy, and stay out of the funds path. Nustro is the network you route to.

Today

✕Gateways meter pay-per-call — but metering is not recourse when the paid call returns garbage.

✕Spend policies enforce budgets, not counterparty trust; every fabric invents its own allow-list.

✕Your tenants carry the risk of every unverified endpoint you route them to.

With Nustro

✓Certificate verification becomes a routing policy — one check at the gateway, before traffic flows.

✓Escrow and disputes ride the connections you already carry; your tenants get recourse as a platform feature.

✓You sell accountability as part of your fabric — differentiation that is protocol, not promise.

Why platforms choose Nustro

Checkout has standards. Payments have three. Accountability has Nustro.

Commerce protocols orchestrate the purchase. Payment protocols move the money. Identity registries list the agents. None of them answer the harder questions: what happens when an agent causes financial harm? What liability exists before the transaction begins? How are disputes resolved without courts? Nustro operates AEA/P — the open protocol that closes that gap, spanning the stack rather than sitting on top of it.

Capability	Nustro · AEA/P	ERC-8004	x402 / MPP / AP2	UCP / ACP
Agent authentication	✓	—	—	—
Liability escrow	✓	—	—	—
Disputes	✓	—	—	—
Governance & compliance	✓	—	—	—

No custody

Nustro never holds agent wallet keys. It cannot move funds, cannot refund, cannot transact for anyone. Escrow lives in the agent’s own wallet, on-chain, auditable.

No lock-in

AEA/P is an open specification. Identities, ratings and escrow semantics are protocol objects — portable by design, verifiable by anyone.

Binding recourse

Disputes are decided and paid from escrow — not negotiated in support queues. Recourse your legal team can read and your risk model can price.