Live on Robinhood Chain Mainnet

The VEYA API
for bounded agents.

The VEYA product API: policy-checked agent runs, validator consensus and verifiable receipts on Robinhood Chain. Agents act only within the tools you allow, and every result comes back with a receipt anyone can verify.

Base URLhttps://api.veyanet.tech
Read the docs →Connect via MCPService health
StatusOperational
NetworkMainnet
Validators3/3 · 2-of-3
Version1.2.12
Endpoints

Everything an agent needs, behind one key.

Contract 0x87dC58…a674 on Robinhood Chain Mainnet.

Wallet sign-in

Sign a message with your wallet and get a session. Product API keys work on every /v1 route.

/auth

Environments & agents

Sandboxed workspaces, agents, tool policies and scoped memory.

/v1/environments

Runs

Policy-checked agent runs with 2-of-3 validator consensus.

/v1/environments/:id/runs

Proofs

Anchor content fingerprints and list your receipts.

/v1/proofs

Chain

Onchain registration and attestations for environments and agents.

/v1/chain

Verify

Check any VEYA receipt from a transaction hash. No key needed.

/api/verify/:tx

Public registry

Read-only view of agents, certificates and executions.

/public

Health

Service, database, validator and anchor readiness.

/health
API key

Get your key from the VEYA app.

Every /v1 route takes a product API key. Verify and public registry routes need none.

Create a key

  1. Open app.veyanet.tech and connect your wallet on the sign-in page.
  2. In the sidebar, under System, open API Keys.
  3. Under Create API key, enter a name (for example “Production MCP”), choose Dev or Live, and click Create.
  4. Copy the secret right away. It is shown once. Dev keys start with veya_dev_, live keys with veya_live_.
Open the VEYA app →
Authorization header
curl https://api.veyanet.tech/v1/environments \
  -H "Authorization: Bearer veya_live_••••••••"
Or the X-Api-Key header
curl https://api.veyanet.tech/v1/proofs \
  -H "X-Api-Key: veya_live_••••••••"
Verify a receipt (no key)
curl https://api.veyanet.tech/api/verify/0xYOUR_TX_HASH

Keep keys on your server. Never put a key in browser code or a public repo. Revoke a key from the same API Keys page.