capability-network / 1.0 · live

Capabilities
for autonomous agents.

A machine-to-machine utility platform. Autonomous agents discover, pay for, and invoke specialized on-chain capabilities through standardized APIs. Usage-based, USDC-settled, no accounts.

Not a chat app. Not a marketplace. Agents are the primary users — humans are secondary.

GET /registry Read the API →
discover.py 
import requests

# 1. Discover
registry = requests.get(
  "https://agentic.advalorem.io/registry"
).json()

# 2. Pick a capability
cap = next(c for c in registry["capabilities"]
              if c["id"] == "bundle-submit")

# 3. Invoke
result = requests.post(
  cap["endpoint"],
  json=bundle_payload,
  headers={"X-Flashbots-Signature": sig}
)
● 7 capabilities · 3 live · 4 planned
The model

Agents rent capabilities.
Not people.

Traditional SaaS
  • — account signup
  • — API key issuance
  • — monthly subscription
  • — dashboard
  • — sales cycle
Capability network
  • + GET /registry
  • + x402 payment per call
  • + temp authorization
  • + invoke, receive, expire
  • + no humans

Any autonomous agent can discover a capability, understand its cost, purchase access, invoke it, and continue its workflow — without human involvement.

Capability catalog

Seven capabilities.
Three live.

Every capability declares its own price, latency, input schema, output schema, and authentication method. The /registry endpoint is the source of truth.

Loading /registry…
View all capabilities → GET /registry →
Invocation flow

Discover · Pay · Invoke

Autonomous Agent
yours, someone else's, ours — same protocol
Discovery
machine-readable JSON catalog · price + schema + endpoint per capability
Payment x402
USDC on Base · atomic settlement · temporary authorization issued
Invocation
any capability provider (us or someone else) satisfies the request
Response + Authorization Expires
agent continues its workflow · no session, no cleanup

Every capability publishes the same shape. Every agent uses the same discovery and invocation flow. The network is the product.

Composition

Chain any capability.

Each step below could be a different provider. AdValorem operates several; over time, external teams register their own capabilities against the same protocol.

research
→
portfolio-analysis
→
contract-simulation
→
bundle-submit
→
settlement

A single agent workflow spanning research, analysis, simulation, execution, and settlement — each step a discrete, priced, invokable capability. Rented, not integrated.

Operational data

Live telemetry, not marketing claims.

Every capability exposes its own status. /status/health aggregates them for programmatic consumption.

  • Loading /status/health…
    telemetry populates on first response
Long-term

Every AI platform is racing for the prompt.
We're building the capability network underneath.

When autonomous agents become the primary users of the internet, they will need a way to discover, price, and consume specialized services from many providers. Not a marketplace, not a directory, not a chat product — a machine-readable capability network with usage-based settlement and no human friction. We already operate the first several capabilities. External providers register their own against the same protocol over time. The network is the asset.