Australian vehicle data for agents

Choose a tool connection.
Or pay for one lookup.

Use MCP with a CSNB API key, or call the HTTP endpoint with an x402-compatible USDC wallet. Both access the Australian vehicle lookup core.

Use x402 · 0.25 USDCSet up MCP

MCP client

Connect with a key

A client that supports remote MCP over HTTP, plus a CSNB Bearer key with an assigned daily quota.

Configuration and tools →

HTTP agent

Authorize a lookup

A compatible x402 wallet with native USDC on Base. No CSNB API key or subscription for this route.

Payment request and retries →

These routes are separate. A RapidAPI key does not authenticate MCP, and an x402 payment does not issue an MCP key or add to its quota.

01 / MCP setup

Give your agent two focused tools.

Request a CSNB key, then add the connection below to a client that supports this configuration format.

{
  "mcpServers": {
    "csnb": {
      "type": "http",
      "url": "https://api.csnb.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CSNB_API_KEY"
      }
    }
  }
}

Client configuration formats vary. Keep the key private and use your client's credential storage where available.

vehicle_lookup

Inputs: country: "AU", plate (a registration plate or VIN), and state. A state is required for a plate; it is optional for a VIN.

coverage

Returns supported countries and state codes so an agent can check availability before querying.

Request a CSNB MCP key

Raw configuration file →

02 / x402 HTTP quickstart

0.25 USDC per successful lookup.

Standard x402 v2, exact EIP-3009, native USDC on Base mainnet (eip155:8453).

  1. Make an unpaid request and read PAYMENT-REQUIRED.
  2. Validate the amount, recipient, token, network and resource URL with your wallet policy.
  3. Use an x402 client to sign an authorization and retry with PAYMENT-SIGNATURE.
  4. Receive the vehicle data and PAYMENT-RESPONSE receipt after settlement succeeds.

Inspect the request without paying

curl --include --get 'https://api.csnb.net/agent/check' \
  --data-urlencode 'country=AU' \
  --data-urlencode 'plate=1ABC123' \
  --data-urlencode 'state=VIC'

# Expected: HTTP 402 + PAYMENT-REQUIRED (base64 JSON)
# This request does not authorize or send a payment.

Authorization comes from your wallet

The 402 header describes the resource and accepted payment. Use an x402 v2 client with an EIP-3009 signer; a normal HTTP client alone does not create a payment authorization.

CSNB verifies the authorization, gets a vehicle record, then initiates settlement. A lookup that fails before settlement is not charged. The successful response is {vehicle: VehicleResult, payment: "paid"}.

Payment headers and complete API schema →

Retry the same authorization

Save the signed payload before sending it. For 202 settlement_pending, 409 payment_processing or a lost response, retry the same URL with the same PAYMENT-SIGNATURE and observe Retry-After.

Do not create a fresh payment while the previous outcome is uncertain. A settled authorization returns its saved result and receipt on replay, including after its authorization deadline.

Plan your integration

Capabilities and boundaries.

Which countries can an agent query?

Australia is live for NSW, VIC, QLD, WA, SA, TAS, ACT and NT. Other countries are not available for paid lookups. Check coverage.

Does the API return owner or history data?

No. The current response provides vehicle identity facts when available. It does not include owner contact details, valuations, a comprehensive history report or proof of current registration. Read the data scope.

Can I send USDC directly?

An optional prepaid invoice route is available, with different matching and retry rules. It is separate from standard x402 and has no automatic refund. Read the direct-transfer documentation before using it.

Where can an agent discover the API?

Use llms.txt for a concise guide and OpenAPI for the machine-readable schema.