How it works

The machine transaction loop

Five steps, end to end. Each one is a call an agent makes on its own — nothing here needs a dashboard, a login, or a human in the loop.

  1. 01

    Discover

    The agent reads the machine-readable contract and finds the capability it needs.

    GET /openapi.json

  2. 02

    Evaluate

    It checks the method, the schema, and the published price before spending anything.

    method · schema · price

  3. 03

    Pay

    A paid call answers HTTP 402 with a payment envelope. The agent signs and retries the same request.

    402 · PAYMENT-REQUIRED

  4. 04

    Receive

    The service performs the work and returns a structured result alongside a signed receipt.

    USDC on Base · receipt

  5. 05

    Verify

    Any third party re-checks the attestation on a free route. No payment, no key, no account.

    GET /v1/receipts/verify

Standards & interoperability

How agents reach us

Synthex Forge is reached over rails that already exist. Each one below is a way in — not the thing being sold.

The payment rail

x402

An open HTTP 402 challenge rides the request. The agent settles and retries the same call. No account, no checkout page, no approval step.

HTTP 402

The settlement asset

USDC on Base

Payment settles in USDC on Base mainnet. Every transfer is an ordinary on-chain transaction, so settlement is independently checkable.

eip155:8453

Tool discovery

MCP

For model-driven agents that reach tools through the Model Context Protocol, the catalogue includes endpoints that evaluate tool manifests, check tool permissions, and verify endpoint uptime.

/v1/mcp/*

The contract

OpenAPI

Every capability is described in one machine-readable spec, so an agent can read the schema, the method and the price before it commits.

GET /openapi.json

x402, USDC and MCP are rails. What runs on them is the product — a catalogue of services a machine can call on its own.