> ## Documentation Index
> Fetch the complete documentation index at: https://tetrafi.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Agentic Netting

> Your agents pay and get paid all day. Net that flow across platforms, not just inside yours, and settle one residual on the chain you choose. Coming soon.

<Note>
  **Coming soon.** Agentic Netting opens to design partners first. Lane: **Designed**. Paths, schemas, and parameters publish at launch.
</Note>

* **Every call pays a toll.** Agents pay per call - for data, inference, tools, and each other - and the settlement cost can outweigh the payment itself.
* **Your batching sees only your book.** The rest of the counterflow sits on other platforms, out of its sight.
* **Earnings land anywhere** - on whatever chain the payer happened to use.

Agentic Netting puts that flow on the [one clearing network](/netting). **Agents create the obligations; the clearing engine nets them** - deterministically, with a proof checked on-chain every run. No agent decides anything.

## What Changes for You

* **Net across platforms, not just inside yours.** The counterflow your own batching can't see cancels too, so less of a day's agent spend ever touches a chain.
* **Keep your stack.** Your x402 facilitator, wallets, and signers stay as they are: batches go in, one residual comes out. No facilitator yet? Run on ours, with netting for payments your payers authorize under a deferred scheme.
* **See the saving before anything moves.** Send real batches in analysis mode and get back what would have netted, with nothing executed - your number, on your own flow.
* **Chains net against each other too.** What your agents earn on one chain offsets what they spend on another, and the residual pays out in the asset and on the chain you choose, over any [supported corridor](/supported-chains).
* **You stay the member.** Your platform is the counterparty of record. Agents act inside [sponsored spending envelopes](/core-concepts/agents) with a kill switch, your end users never enter the graph, and your flow stays [private](/netting/privacy-and-control) - from other platforms and from TetraFi.

## A Day of Flow

Agents settling on three different rails, one day, USDC:

* Agents on **an exchange** owe agents on **Base** - **100 USDC**
* Agents on **Base** owe agents on **Arbitrum** - **80 USDC**
* Agents on **Arbitrum** owe agents on **the exchange** - **60 USDC**

Gross, that is 240 USDC across three settlements, each a bridge or a venue withdrawal. Netted, the loop of 60 cancels with **nothing crossing a chain or leaving a venue**, and the rest settles along debts that already exist: the exchange's agents pay Base 40, Base pays Arbitrum 20. **60 moves instead of 240.**

## How It Enters

Your facilitator or channel store sends batches of served-but-unpaid usage; from there it is the standard [integration](/netting-api/integration). What counts as nettable, analysis mode, and payouts are in [Build: Agentic Netting](/netting-api/agentic-netting).

<CardGroup cols={2}>
  <Card title="Build Agentic Netting" icon="code" href="/netting-api/agentic-netting">
    Batches from your stack, analysis mode, payouts on any chain.
  </Card>

  <Card title="Trading & Payments" icon="arrow-right-arrow-left" href="/netting/trading-and-payments">
    Desk and corridor flow on the same network - more counterflow for your agents' spend.
  </Card>
</CardGroup>

Run an agent platform? [Start the conversation](/support) - tell us how your agents pay and get paid.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.