veya

VEYA

VEYA makes agent work verifiable. An agent runs inside a scoped environment with an explicit tool allowlist. Its work is checked by 2-of-3 consensus or run in AES-256-GCM sealed execution, hashed with BLAKE3-256, signed with ML-DSA-44, and anchored on the Veya.sol protocol contract on Robinhood Chain. Anyone can verify the record from a tx hash.

environment → agent (+ allowedTools) → consensus / sealed execution
  → BLAKE3 digest + ML-DSA signature → Veya.sol (Robinhood Chain) → verify

Before anything

1. If no veya_* tools are available, tell the user to add the MCP server

https://mcp.veyanet.tech/mcp (configs in references/setup.md) and stop.

1. Call veya_describe. Read settlement.network, settlement.contract, settlement.explorer.

Use that network and explorer in every answer.

Access

• Public (no key): describe, ping, health, hashing, veya_prove without anchor, all verify and on-chain reads, veya_pq_*, public registry.
• API key: pass the user's product key (veya_dev_… / veya_live_…) as the apiKey argument. Get one at https://app.veyanet.tech (connect wallet → System → API Keys). Needed for environments, agents, policy, routing, memory, consensus, sealed execution, veya_seal_decision.
• API key + wallet: on-chain writes also need the funded wallet bound to that key (payerPrivateKey). Gas is ETH on the selected network.
• Limits: consensus, sealed execution and veya_seal_decision allow 30 calls/min per key. host-sent seals: 20 per key and 100 per host per UTC day. /mcp: 120 requests/min per IP.

Details: references/auth-and-limits.md.

Decision flow

Workflow 1: prove content (no key)

{ "tool": "veya_prove", "arguments": { "text": "hello" } }

Pass exactly one of text, json (a JSON string), txHash. Expect ok: true, mode: "digest", digestHex, anchored: false. hello → ea8f163db38682925e4491c5e58d4bb3506ef8c14eb78a86e908c5624a67200f. To anchor: add anchor: true, environmentId (an environment already on Veya.sol), apiKey, payerPrivateKey. Expect mode: "anchored", txHash, explorerUrl.

Workflow 2: verify a transaction

Example Mainnet receipt (execution attestation): 0x91550fdd7a60616e3157364d3624d423403c4add2590c36d3ba290fa07cb95cc.

1. veya_verify_transaction { txHash } → Veya.sol events and digest.
2. veya_verify_commitment_onchain { txHash } → for commitment txs, confirms commitments(digest) is still true (commitmentChecks is empty for attestations and registrations).
3. Report network, event, digest, and {explorer}/tx/{txHash}. If to is not Veya.sol, say it is not a VEYA proof.

Workflow 3: workspace → agent → policy

1. veya_account { apiKey } → confirm the wallet.
2. veya_create_environment { apiKey, name, type? } → environmentId (type: research default, governance, treasury, contributor, protocol, desci).
3. veya_deploy_agent { apiKey, environmentId, permissionConfig: { allowedTools: [...] } } → agentId. List every tool the agent needs.
4. veya_set_tool_policy { apiKey, environmentId, agentId, tool, allowed } to adjust.
5. Optional: veya_register_environment { apiKey, payerPrivateKey, environmentId } puts it on-chain.

Workflow 4: consensus → attestation

1. veya_api_health → validators reachable.
2. veya_run_consensus { apiKey, taskId, payload } → require consensus_reached: true; take agreed_blake3_hash.
3. veya_pq_sign { message: <hash>, privateKeyHex } → signatureHex.
4. veya_attest_execution { apiKey, payerPrivateKey, environmentUuidHex, blake3HashHex, mldsaSigHex } → txHash, from.
5. veya_verify_transaction { txHash }.

Rules

1. Start read-only; write only when the user asks for an on-chain result.
2. Before a write: state the network (Robinhood Chain Mainnet unless Testnet was selected), run veya_writes_status, and get the user's confirmation.
3. Use keys only inside tool arguments; never repeat them in replies or store them in memory.
4. Hex: UUIDs are 16 bytes (32 hex), digests 32 bytes (64 hex); 0x optional.
5. Use veya_run_consensus (veya_client_run_consensus is a deprecated alias).
6. Never attest when consensus_reached is false.
7. If a write returns warning, the chain write succeeded; do not resend.
8. After every write, return txHash, the explorer link and from.
9. Describe VEYA only as what it does: it checks, limits, records and proves agent actions. It does not trade, connect to exchanges, hold or move user funds, or read price or market data.

Errors

Full list: references/troubleshooting.md.

Custom logic

For custom pipelines or local signing, use @veyanet/sdk (same capabilities as code): references/sdk.md.

Links

• App and API keys: https://app.veyanet.tech
• Docs: https://veyanet.tech/docs
• SDK: https://github.com/veyanet/veya-sdk
• MCP server: https://github.com/veyanet/veya-mcp