Developer entry point

Start with the contract.
Inspect every response.

Use the existing machine surface for tools and discovery. Use the examples to understand supplied-record reconciliation.

01 / Discover

Inspect the manifest before selecting a tool. Read its input, price and scope.

Root manifest · MCP discovery · UCP discovery

02 / Try a check

The sample may use an available free allowance. If the server responds with HTTP 402, inspect the payment requirements. This example does not sign or submit a payment.

03 / Read the result

Inspect the check result and any returned receipt. An HTTP 200 alone does not mean an identifier is valid. No receipt should be inferred when none is returned.

curl https://hcrb.in/?format=json

curl https://hcrb.in/v1/tools/iban-check/call \
  -H 'Content-Type: application/json' \
  -d '{"input":{"iban":"GB82WEST12345698765432"}}'

Requests above contact the live service when you run them. Nothing runs automatically on this page.

{
  "mcpServers": {
    "code402": {
      "url": "https://hcrb.in/mcp"
    }
  }
}

For MCP clients that support remote HTTP server configuration. Client setup varies.

Full integration guide ↗

Capability catalog

Read the shared product scope and distinguish tools, demonstrations and proposed integrations.

Open catalog →

Reproducible examples

Inspect both source records and computed results. No account or payment is needed.

Open example JSON →

Existing API contracts

Use the machine surface for authenticated calls and the published API specification.

OpenAPI specification →

Supplied-record comparison

Use the same engine in your workflow.

POST /commerce/reconcile accepts an order, payment records and delivery records as JSON. The response distinguishes mismatches from missing evidence. This is a stateless comparison: records are not retained by this handler, no payment executes, and no third-party settlement or delivery is verified.

curl YOUR_BASE_URL/commerce/reconcile \
  -H 'Content-Type: application/json' \
  --data-binary @records.json

Use the input object from one of the example records to try the contract. Limits: 65,536 request bytes, 100 payment records and 100 delivery records. Amounts and units are integer strings; timestamps are integer epoch milliseconds.

A well-formed comparison returns HTTP 200 even when records disagree. Inspect status and issues. Invalid schemas return 422; malformed JSON returns 400; oversized input returns 413. No automatic retries or charges occur.

Browser calls are restricted to the same origin. Server clients should send no credentials or secrets with these records. Use redacted identifiers when evaluating the service.

Run entirely on your machine

node hcrb/scripts/commerce.mjs examples
node hcrb/scripts/commerce.mjs reconcile records.json

The local CLI performs no network requests. Exit codes: 0 records agree; 2 review required or evidence incomplete; 1 file or input error.

Start with the contract.Inspect every response.