Developers
Contract Addresses
These are the token contracts Numerari supports, and the one third-party contract it builds on. Always compare an address here with the explorer link before you rely on it.
Early access
The Agent API and the numerari-agent kit that use these contracts are in early access. The Agent API is deployed at https://api.numerari.io/api/agent/v1; the kit is not yet published for public download.
Supported tokens
| Token | Network | Chain ID | Decimals | Contract |
|---|---|---|---|---|
| USDC | Base | 8453 | 6 | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| USDT | Ethereum | 1 | 6 | 0xdAC17F958D2ee523a2206206994597C13D831ec7 |
Both tokens use six decimals, not the eighteen common to many other tokens. The relay and the kit only recognise these exact contracts on these exact chains.
Not supported
- USDT on Base. The only USDT-labelled contract there is a third-party bridged token that Tether does not issue, so Numerari does not treat it as USDT.
- USDC on Ethereum, and any token on a chain not listed above.
Third-party contract: 0xSplits
Numerari’s hosted checkout splits an incoming amount between the platform fee and the merchant using 0xSplits’ own contracts rather than a custom one. This is 0xSplits’ factory, not a Numerari contract. Numerari does not control it.
| Contract | Network | Chain ID | Address |
|---|---|---|---|
| PullSplitFactory (SplitV2), by 0xSplits | Base | 8453 | 0x6B9118074aB15142d7524E8c4ea8f62A3Bdb98f1 |
Each merchant gets their own split contract created through this factory. Those per-merchant addresses are specific to the merchant and are not listed here.