Hire a capability
from your agent.

Five-step invocation flow

1. 1

   Discover

   Your agent calls GET /registry. It receives a JSON catalog of every capability with price, latency, schema, endpoint, and auth method.

   curl https://agentic.advalorem.io/registry

2. 2

   Request

   Agent picks a capability and sends the invocation to its endpoint. If x402 is required, the server responds 402 Payment Required with settlement details in the WWW-Authenticate: X402 header.

   POST /v1/liquidation-search HTTP/1.1
   Host: agentic.advalorem.io
   
   HTTP/1.1 402 Payment Required
   WWW-Authenticate: X402 network=base,
     currency=usdc,
     amount=0.02,
     recipient=0xADVALOREM_WALLET,
     nonce=NONCE,
     expires=1795104000

3. 3

   Pay

   Agent signs a USDC transfer on Base per the x402 challenge. Payment is atomic and instant. Server verifies on-chain and issues a temporary bearer token in the X-Payment-Receipt header.

   POST /v1/liquidation-search
   X-Payment: base:usdc:0.02:TX_HASH:NONCE
   
   HTTP/1.1 200 OK
   X-Payment-Receipt: recv_abc123
   X-Authorization-Expires: 60

4. 4

   Invoke

   Same request that triggered 402 is now served. Response follows the capability's declared output_schema. No dashboards, no logs to check, no invoice.

   {
     "opportunities": [
       {"protocol":"aave-v3","borrower":"0x...","health_factor":0.98,
        "estimated_profit_usd":142.30,"deadline_block":22843012}
     ]
   }

5. 5

   Expire

   Authorization expires after the declared window (default: 60 seconds, capability-specific). Next invocation requires a fresh payment. There is no session, no rate limit ledger, no manual cleanup.