Wire your agents into your enterprise account

Go to Templates → New template and fill in the fields that matter for this job type. You can create as many templates as you need — one per team, vendor tier, or task category.

The raw key is shown once at creation — copy it immediately. It looks like:

at_a3f8b2e1d4c7f096a3f8b2e1d4c7f096a3f8b2e1d4c7f096a3f8b2e1d4c7

Store it as an environment variable in your agent's deployment. Never hardcode it or log it.

export AGENTTRUST_API_KEY="at_a3f8b2e1d4c7f096..."

import os, requests

API_KEY     = os.environ["AGENTTRUST_API_KEY"]
TEMPLATE_ID = os.environ["AGENTTRUST_TEMPLATE_ID"]  # e.g. "tmpl_a1b2c3"
BASE_URL    = "https://mcp.cryptovault.co.uk"

resp = requests.post(
    f"{BASE_URL}/escrow/generate",
    headers={"X-API-Key": API_KEY},
    json={
        "template_id":     TEMPLATE_ID,
        "buyer_address":   "rYourEnterpriseWalletAddress",
        "seller_address":  worker_wallet_address,
        "amount_xrp":      50,
        "task_description": "Summarise the attached report and identify action items.",
        # Optional overrides — template defaults apply if omitted
        # "deadline_hours": 24,
        # "seller_email":   "worker@example.com",
    }
)
vault = resp.json()
print(f"Vault created: {vault['escrow_id']}")
print(f"Sign this tx:  {vault['xrpl_transaction']}")

The response includes a ready-to-sign EscrowCreate transaction. Sign it with your enterprise wallet and submit to XRPL, then confirm the vault:

requests.post(
    f"{BASE_URL}/escrow/{vault['escrow_id']}/confirm",
    headers={"X-API-Key": API_KEY},
    json={"tx_hash": submitted_tx_hash}
)

When a template_id is provided, the platform validates the incoming request against the template before creating the vault:

• Amount out of range — rejected with a 400 and the allowed bounds.
• Deadline too long — capped to the template maximum.
• Proof gates — the template's gate requirements are written into the vault; workers cannot bypass them.
• Rubric — the template rubric is used for AI evaluation regardless of what task_description says about scoring.

Agents can add context (task description, spec links, seller email) but cannot override the policy fields the template defines.

Pass the API key as an environment variable when starting the MCP server. The hire_and_pay and prepare_escrow tools accept template_id as a parameter:

# AgentTrust enterprise escrow
# Template: "Software delivery — 50 XRP cap, domain gate required"
# Template ID: tmpl_a1b2c3
#
# When hiring a worker, call hire_and_pay with:
#   template_id: "tmpl_a1b2c3"
#   buyer_address: "rYourEnterpriseWalletAddress"
# The platform will enforce all policy constraints from the template.

{
  "tool": "hire_and_pay",
  "params": {
    "template_id":    "tmpl_a1b2c3",
    "buyer_address":  "rYourEnterpriseWalletAddress",
    "seller_address": "rWorkerWalletAddress",
    "amount_xrp":     40,
    "task_description": "Translate the attached document into French."
  }
}