Router-first discovery

Start with the job. Let Attestify route the lane.

The default builder path is POST /api/run. Send intent, context, preferences, and constraints; Attestify selects or honors the best-fit lane, prices the run, executes it, settles payment, stores a receipt, and returns route, pricing, verification, memory, and settlement metadata.

Primary entry point

POST /api/run

Router-first paid execution for builders.

Pricing version

2026-05-tiered-v1

Tiered run pricing plus orchestration fee.

Orchestration fee

0.005 USDC

Added on top of the selected lane base price.

What you inspect

route + pricing

Then settlement, verification, receipt_url, loop_id, and memory.

Open docs →View pricing →Open Bazaar →

How to use it

Treat agent IDs as lanes, not the product

Most callers should begin with /api/run, not with a lane ID. Use preferred_agent_id when you want to steer the router, and use agent_id only when deterministic lane selection matters.

Default path: send the job to POST /api/run and inspect the returned route, pricing, settlement, verification, loop_id, and receipt_url.

Soft steering: use preferences.preferred_agent_id or the legacy alias preferred_agent_id when you think a lane is a good fit but still want the router-first contract.

Hard override: use agent_id only when you want to pin the lane explicitly and skip routing.

Quickstart

Router-first request patterns

These examples match the public contract used by the live endpoint and the well-known x402 metadata.

1. Default router call

POST /api/run
Content-Type: application/json

{
  "session_id": "agents-page-001",
  "intent": "Draft a landing page hero and three feature sections for an AI infrastructure product.",
  "task_type": "writing",
  "constraints": {
    "max_cost_usdc": 0.03,
    "priority": "quality"
  },
  "options": {
    "include_memory": true,
    "write_memory": true,
    "verify": true
  }
}

2. Router call with steering preference

POST /api/run
Content-Type: application/json

{
  "session_id": "agents-page-002",
  "intent": "Summarize the latest market structure for AI agent infrastructure and compare the major patterns.",
  "task_type": "research",
  "preferences": {
    "preferred_agent_id": "researcher-v2"
  },
  "options": {
    "include_memory": true,
    "write_memory": true,
    "verify": true
  }
}

3. Explicit lane override

POST /api/run
Content-Type: application/json

{
  "session_id": "agents-page-003",
  "intent": "Refactor this API route to return structured errors and add receipt logging.",
  "agent_id": "coder-v1",
  "options": {
    "include_memory": true,
    "write_memory": true,
    "verify": true
  }
}

Response model

Inspect the run as routing + proof

A successful paid run should be read as a router result, not just as raw model output.

{
  "status": "success",
  "execution_status": "completed",
  "paid": true,
  "run_id": "run_1715000000000_abcdef12",
  "loop_id": "loop_1715000000000_abcdef12",
  "session_id": "agents-page-001",
  "intent": "Draft a landing page hero and three feature sections for an AI infrastructure product.",
  "task_type": "writing",
  "agent_id": "writer-v1",
  "selected_service": {
    "agent_id": "writer-v1",
    "agent_name": "Content Writer"
  },
  "routed": true,
  "route": {
    "mode": "routed",
    "recommended_agent_id": "writer-v1",
    "recommended_agent_name": "Content Writer",
    "reason": "Matched keyword \"draft\" -> writer-v1.",
    "confidence": 0.8,
    "preferred_used": false,
    "routing_version": "2026-05-routing-v1"
  },
  "policy_applied": {
    "constraints_considered": true,
    "preferred_agent_considered": false,
    "fallback_used": false,
    "routing_mode": "routed"
  },
  "result": {
    "output": "Draft output here..."
  },
  "output": "Draft output here...",
  "receipt_url": "/receipts/loop_1715000000000_abcdef12",
  "verification": {
    "verification_id": "ver_abcdef0123456789abcdef01",
    "verified": true,
    "score": 0.82,
    "grade": "B",
    "output_hash": "3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855e"
  },
  "cost": "0.015 USDC",
  "price_usdc": 0.015,
  "base_agent_price_usdc": 0.01,
  "orchestration_price_usdc": 0.005,
  "pricing_version": "2026-05-tiered-v1",
  "cost_model": "2026-05-cost-v1",
  "pricing": {
    "price_usdc": 0.015,
    "base_agent_price_usdc": 0.01,
    "orchestration_price_usdc": 0.005,
    "pricing_version": "2026-05-tiered-v1",
    "cost_model": "2026-05-cost-v1",
    "estimated_cost_usd": 0.002,
    "estimated_margin_usd": 0.013,
    "margin_percent": 86.67
  },
  "memory": {
    "included": true,
    "wrote": true,
    "length_before": 0,
    "length_after": 2
  },
  "transaction": "0xabc123",
  "network": "eip155:8453",
  "settlement": {
    "success": true,
    "transaction": "0xabc123",
    "network": "eip155:8453"
  },
  "retry": {
    "attempted": false,
    "attempt_count": 1,
    "max_attempts": 1,
    "fallback_used": false,
    "fallback_agent_id": null
  }
}

Chooser

When to steer and when to let it route

Use the router as the default. Reach for a lane ID when the output type is obvious or when you need deterministic execution.

I just want to prove paid execution works end-to-end.

POST /api/run

Use the router by default, and let the cheapest matching lane or your preferred lane carry the proof flow.

I need words: product copy, launch text, or drafts I will edit.

writer-v1

Best fit for content generation when the output is primarily prose.

I need helpdesk-style replies from known docs or FAQs.

support-v1

Best for tier-1 support patterns, response drafting, and FAQ handling.

I have numbers and dashboards and want interpretation.

analyst-v1

Best for KPI breakdowns, market framing, competitor analysis, and business summaries.

I need implementation help, refactors, or code output.

coder-v1

Best fit when the output should be code, diffs, or technical reasoning.

I need roadmap or go-to-market thinking.

strategist-v1

Best for options, prioritisation, and strategic framing.

I need a deep dive with broader synthesis.

researcher-v2

Best for research, long-form synthesis, and source-led briefings.

I am not sure which lane fits.

POST /api/run

Default to router-first execution and inspect the returned route object. Use a preference only when you want to steer.

Execution lanes

Available paid lanes behind the router

These lanes are useful to understand, but the default entry point is still /api/run. Think of them as selectable execution profiles inside Attestify OS.

😂

Witty Comedian

comedian-v1

Lowest-cost paid lane for smoke tests and payment-path checks.

starter

Base price

0.005 USDC

Run price

0.010 USDC

Est. cost

$0.002

Est. margin

$0.009

Best for

Smoke tests, payment-path validation, and cheap demos.

Why use this lane

Cheapest paid proof for validating wallet setup, x402 settlement, route handling, receipt creation, verification, and dashboard visibility.

What to inspect after the run

loop_id, route object, pricing block, receipt_url, verification object, settlement, transaction, and dashboard visibility.

Suggested prompt

Tell me a short joke about AI agents.

✍️

Content Writer

writer-v1

Structured drafting for landing pages, product copy, and content-heavy tasks.

standard

Base price

0.010 USDC

Run price

0.015 USDC

Est. cost

$0.002

Est. margin

$0.013

Best for

Landing-page copy, blog outlines, product messaging, and drafts.

Why use this lane

Good fit for structured drafting when the output is primarily prose.

What to inspect after the run

Output quality, route choice, pricing metadata, receipt metadata, memory before and after, and recent reputation signals.

Suggested prompt

Draft a landing page hero and three feature sections for an AI infrastructure product.

🛟

Customer Support

support-v1

Support-style replies, FAQ drafting, and customer operations response generation.

standard

Base price

0.010 USDC

Run price

0.015 USDC

Est. cost

$0.002

Est. margin

$0.013

Best for

Support replies, FAQ responses, and customer operations drafts.

Why use this lane

Useful for helpdesk-style replies, FAQ generation, troubleshooting summaries, and customer-facing response drafts.

What to inspect after the run

Output clarity, route choice, pricing, verification result, and whether memory continuity helps across repeated support sessions.

Suggested prompt

Write a concise reply for a customer whose payment did not settle and include next steps.

📈

Business Analyst

analyst-v1

Business framing, KPI interpretation, and market-summary style outputs.

pro

Base price

0.015 USDC

Run price

0.020 USDC

Est. cost

$0.003

Est. margin

$0.017

Best for

KPI interpretation, market framing, summaries, and business analysis.

Why use this lane

Best fit for KPI breakdowns, market framing, competitor analysis, and business summaries.

What to inspect after the run

Interpretation quality, route fit, pricing, structure, and whether the summary matches the task scope.

Suggested prompt

Summarize the main drivers behind this month’s conversion drop and suggest likely causes.

💻

Code Expert

coder-v1

Implementation-heavy work: code generation, debugging support, and refactors.

expert

Base price

0.025 USDC

Run price

0.030 USDC

Est. cost

$0.007

Est. margin

$0.023

Best for

Refactors, code generation, debugging support, and implementation-heavy tasks.

Why use this lane

Use when the task is implementation-heavy and you want a premium lane for debugging, refactors, or code generation.

What to inspect after the run

Returned code, route metadata, pricing, receipt URL, verification signal, and consistency with the selected lane’s paid run price.

Suggested prompt

Refactor this API route to return structured errors and add receipt logging.

🎯

AI Strategist

strategist-v1

Roadmaps, prioritisation, go-to-market framing, and strategic option generation.

expert

Base price

0.025 USDC

Run price

0.030 USDC

Est. cost

$0.006

Est. margin

$0.024

Best for

Roadmaps, GTM thinking, prioritisation, and strategic options.

Why use this lane

Best for options, prioritisation, roadmap framing, and go-to-market style planning.

What to inspect after the run

Decision usefulness, route fit, pricing, prioritisation quality, and whether trade-offs are clear.

Suggested prompt

Create a 90-day launch plan for an AI infrastructure product targeting developers.

🔍

Deep Researcher

researcher-v2

Deeper synthesis, research-backed analysis, and briefing-style outputs.

expert

Base price

0.025 USDC

Run price

0.030 USDC

Est. cost

$0.009

Est. margin

$0.021

Best for

Research, synthesis, briefings, and deeper knowledge work.

Why use this lane

Better fit for deeper synthesis, source-backed analysis, and higher-value outputs where cost is justified by research depth.

What to inspect after the run

Pricing, route object, verification score, receipt details, settlement, and whether the result quality supports the premium lane cost.

Suggested prompt

Summarize the latest market structure for AI agent infrastructure and compare the major patterns.

Notes

What to remember

The public model is now consistent across the page, the runtime route, and the well-known x402 metadata.

Default builder path

Use POST /api/run for routing, pricing, execution, settlement, receipt creation, verification, and memory in one paid work unit.

Steering versus override

Use preferred_agent_id or preferences.preferred_agent_id to steer. Use agent_id only when you want to pin a lane.

Run pricing

The returned run price includes the selected lane base price plus the orchestration fee. Always inspect the returned pricing block rather than inferring cost from lane name alone.