> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Tempo USDCe payments

> Accept USDCe (TIP-20) on Tempo: EVM style settlement, amount only binding, and x402, MPP, AP2 and AgentCash on Tempo mainnet and Moderato testnet.

## At a glance

|                     | Mainnet                                      | Moderato (testnet)    |
| ------------------- | -------------------------------------------- | --------------------- |
| Network ID          | `tempo:mainnet`                              | `tempo:moderato`      |
| Native asset        | ETH                                          | ETH                   |
| Native decimals     | 18                                           | 18                    |
| Stablecoin          | USDCe (TIP-20)                               | USDCe (TIP-20)        |
| Stablecoin contract | `0x20c000000000000000000000b9537d11c60e8b50` | (Moderato equivalent) |
| Stablecoin decimals | 6                                            | 6                     |
| Confirmation time   | About 2 seconds                              | About 2 seconds       |
| Typical fee         | Sub-cent                                     | Free (testnet faucet) |

## Amount-only binding

Tempo is EVM-style, like Base. TIP-20 transfers don't carry a memo, so AlgoVoi uses amount uniqueness to bind checkouts to specific transfers. Same caveats as [Base](/chains/base): send the exact `amount_microunits` from the checkout response.

## TIP-20 versus ERC-20

TIP-20 is Tempo's token standard, semantically equivalent to ERC-20 for the operations AlgoVoi cares about (`transfer`, `transferFrom`, `balanceOf`). The contract above is the canonical USDC bridge token, marked USDCe to distinguish it from native USDC on Ethereum mainnet.

## Wallets

EVM-compatible wallets work, configured for the Tempo network:

* [AlgoVoi Chrome extension](https://chromewebstore.google.com/detail/algovoi/ofmgegnkjdmbeakjbmfaagigmhagdcbl) (in-house wallet, native x402 / MPP / AP2 on Tempo via viem `signTransaction` + ERC-20 `transfer` for USDCe; six-chain coverage as of v2.6.0)
* [MetaMask](https://metamask.io)
* [Rabby](https://rabby.io)
* [WalletConnect](https://walletconnect.com)

## AgentCash

[AgentCash](https://agentcash.dev) is the reference MPP client for Tempo. It manages a USDCe wallet on Tempo mainnet, resolves `WWW-Authenticate: Payment` challenges automatically, and broadcasts signed transactions — no configuration needed.

```bash theme={null}
# Install and fund
npm install -g agentcash   # or use npx
npx agentcash deposit      # get your wallet address and top up with USDCe

# Call any AlgoVoi MPP endpoint
npx agentcash fetch https://api.algovoi.co.uk/mpp/probe -m GET
npx agentcash fetch https://api.algovoi.co.uk/mpp/{tenant_short_id}/{resource_id} -m GET
```

Payments settle on Tempo in about 2 seconds. The AlgoVoi gateway accepts the resulting transaction hash, verifies it on-chain, and returns a JWT receipt.

## Agent-to-agent settlement on Tempo

Tempo is a payments-focused EVM network, and the mesh settles there the way it settles on any EVM chain: the `execution_ref` rides in the transaction calldata.

[AlgoVoi Mesh](/agent-mesh) settles a payment directly between two autonomous agents on Tempo. Each agent verifies the other offline with a Falcon-1024 credential, the pair negotiates Tempo as the settlement chain, and the authorized decision is anchored in the transaction calldata as one content-addressed `execution_ref`. There is no facilitator, no per-transaction fee, and no AlgoVoi service in the trust path at settlement time.

**Proven on-chain.** A mutually verified Falcon-1024 pair negotiated Tempo and settled once:

| Network       | Anchors in | Transaction                                                                                                              |
| ------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------ |
| Tempo testnet | calldata   | [0xd27c45d6...](https://explore.testnet.tempo.xyz/tx/0xd27c45d6a546ce7444e31c0cdfb9fa2479a730e7ba21da7eef6f777699947e58) |

The transaction calldata carries the 32 byte `execution_ref` (`9d2fc17e...`) that run's handshake produced. Recompute it yourself from the raw fields with a stock RFC 8785 (JCS) implementation and SHA-256 and compare; no AlgoVoi software is involved in checking it.

The chain never verifies Falcon. It only carries the anchor, which is why the same agent trust works on Tempo and on every other chain the pair could have chosen. See [AlgoVoi Mesh](/agent-mesh) for the mutual handshake, the signed chain-offer negotiation, and the full eight-chain proof.

## See also

* [Base](/chains/base) for the other EVM chain we support
* [x402 protocol](/protocols/x402) for the payment protocol layer
* [MPP protocol](/protocols/mpp) for method-level paywalls and AgentCash integration