Every paid service, also a tool.
Synthex Forge sells machine-native services that agents pay for per call over x402 — and every one of them is callable as an MCP tool. 105 tools are live right now, 103 of them paid and priced between $0.01 and $29.00. No API keys. No signup. The payment is the authentication.
POST https://x402.synthexforge.com/mcp
- Transport
- Streamable HTTP
- Protocol
- JSON-RPC 2.0 · MCP 2025-06-18
- Discovery
- POST
tools/list— no payment required - Credential
- None. The payment is the credential.
One endpoint serves every tool. An agent lists the tools, picks the one it needs, calls it, and pays the price the server quotes — in the same round trip, over one HTTP request. The same catalogue is available as a plain OpenAPI specification for agents that would rather not speak MCP.
Adding us is a config block.
Four clients, four shapes. Copy the block, point it at the endpoint, and the tools are available to your agent — the wallet that pays for the calls is the client's own.
{
"mcpServers": {
"synthex-forge": {
"type": "http",
"url": "https://x402.synthexforge.com/mcp"
}
}
}A client that cannot pay per call will still list the tools and receive the payment terms in the result — the caller then signs the authorisation and retries. The synthex-x402 SDK does the 402 → sign → retry loop in a single call, on PyPI and npm.
The catalogue, priced per call.
Generated from the live tools/list response at build time. Every row is a real tool the server is serving right now, with the price it charges — between $0.01 and $29.00.
Agent
1 toolAgent reputation
2 toolsAudit
1 toolBestex
1 toolBudget
1 toolBureau
3 toolsCompliance
1 toolContainment
1 toolContract
1 toolCorpus
1 toolCounterparty
1 toolCredentials
1 toolData
4 toolsDecision
1 toolDispute
1 toolEbook
1 toolEdge
2 toolsEvidence
2 toolsFinance
2 toolsFund
1 toolGovernance
2 toolsIdentity
2 toolsIndex
1 toolInvoice ocr
1 toolLatency
1 toolLicence
1 toolMandate
1 toolMarket
5 toolsMcp
3 toolsMemory
2 toolsNav
1 toolOutput
1 toolPass
2 toolsPayment
2 toolsPolicy
1 toolPortfolio
1 toolPreflight
1 toolPretrade
1 toolProcurement
1 toolQuant
4 toolsQuota
1 toolRates
1 toolReadiness
1 toolReceipts
1 toolResearch
1 toolRoute
1 toolSec extract
1 toolSecurity
3 toolsSettlement
4 toolsSigned research
1 toolSla
1 toolSme
1 toolSocial
1 toolSpend
2 toolsStrategy
2 toolsSynthesis
1 toolTask
1 toolUptime
1 toolUtils
6 toolsVerdict
5 toolsVerify catalog
1 toolVeritrack
1 toolX402
3 toolsHealth
1 toolThe payment is the authentication.
There is no account to create, no key to store and no checkout page. An agent proves it can pay by paying.
Call the tool with no payment header
The request goes out like any other HTTP call. There is no key to attach, because there is no account to attach it to.
The server answers with payment terms
An unpaid call returns a payment_required payload carrying the exact amount in atomic USDC, the asset, the network (eip155:8453), the payTo address and the scheme. The price travels with the response — nothing had to be looked up in advance.
Sign an EIP-3009 authorisation
The caller signs a transferWithAuthorization for that exact amount, base64-encodes it, and puts it in the X-PAYMENT header. One signature, no account, no checkout page.
Retry the identical call with X-PAYMENT
The identical request is resent with the payment header. The authorisation settles USDC on Base mainnet and the tool runs, and the caller receives the signed result.
Settlement is USDC on Base mainnet, chain eip155:8453, using the EIP-3009 transferWithAuthorization scheme — the authorisation is signed once, by the agent's own key, and consumed on the same request. The server publishes the price in the payment terms it returns, so the amount signed is always the amount charged.
No key and no account are needed. That is the whole point: the request carries the authorisation, the authorisation carries the money, and the money is the credential.