Attestify OS
Quickstart
Builder PlansLIVE DashboardControl PlaneHow it worksAgentsPay-per-callDocsFAQs
Home · How it works · Pay-per-call · Team plans · Docs · FAQs
How lanes fit into Attestify

Lanes are the callable execution profiles inside Attestify OS — but they are not the integration surface. The integration surface is the Router (POST /api/run). You send work to the Router; the Router selects the right lane, enforces governance, settles payment, and returns a signed receipt. You can steer lane selection with preferred_agent_id, or pin a specific lane with agent_id when you need deterministic execution.

Lanes — machine-readable facts
entry_point: POST https://attestifyos.com/api/run
discovery: GET https://attestifyos.com/api/lanes (returns all lane_ids, prices, capabilities)
steer_field: preferred_agent_id (soft — Router may override)
pin_field: agent_id (hard — deterministic lane selection)
orchestration_fee: 0.005 USDC added to every run
settlement_asset: USDC on eip155:8453
receipt_field: receipt_url in every successful response
verification_field: verification.verified + verification.score + verification.grade
lanes: comedian-v1 | writer-v1 | support-v1 | analyst-v1 | coder-v1 | strategist-v1 | researcher-v2
cheapest_lane: comedian-v1 @ 0.005 USDC base (0.010 USDC paid run price)
pricing_version: 2026-05-tiered-v1
Router-first discovery

Lanes are callable profiles behind the Router, not the integration surface.

The default builder path is POST /api/run. Send a task with optional preferred_agent_id, optional agent_id, budgets, policies, memory options, verification, and idempotency controls. The Router dispatches to the right lane, evaluates governance, settles payment, and returns decision, pricing, evidence, verification, memory, and settlement metadata.

Primary entry point
POST /api/run
Router-first paid execution for builders.
Steering field
preferred_agent_id
Nudge the Router without hard-pinning.
Override field
agent_id
Use only when deterministic lane selection matters.
Pricing rule
Base + orchestration
Lane base price + 0.005 USDC orchestration fee.
How to think about it

Treat lane IDs as routing targets

Most builders should begin with POST /api/run, not with a lane ID. Use preferred_agent_id when you want to steer the Router, and use agent_id only when explicit lane selection matters.

Default path: send the task to POST /api/run and inspect the returned route, decision, pricing, receipt_url, verification, memory, and settlement.
Soft steering: use preferred_agent_id when you think a lane is a good fit but still want router-first execution and route visibility.
Hard override: use agent_id only when you want deterministic lane selection or already know the exact execution lane.
Request patterns

Router-first examples

These examples reflect the public POST /api/run contract.

1. Default router call — let the Router choose
{ "session_id": "lanes-page-001", "task": "Draft a landing page hero and three feature sections for an AI infrastructure product.", "options": { "include_memory": true, "write_memory": true, "verify": true }, "idempotency_key": "idem-lanes-page-001" }
2. Steered call — preferred_agent_id
{ "session_id": "lanes-page-002", "task": "Summarize the latest market structure for AI agent infrastructure.", "preferred_agent_id": "researcher-v2", "budget": { "max_price_usdc": 0.03, "soft_max_price_usdc": 0.025, "strict": true, "currency": "USDC" }, "options": { "include_memory": true, "write_memory": true, "verify": true }, "idempotency_key": "idem-lanes-page-002" }
3. Pinned call — agent_id
{ "session_id": "lanes-page-003", "task": "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 }, "idempotency_key": "idem-lanes-page-003" }
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 fitting lane or a soft preference carry the proof flow.
I need words: product copy, launch text, or drafts I will edit.
writer-v1
Steer with preferred_agent_id when the output is mostly prose and you still want router-first execution.
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
Use agent_id only when you want deterministic lane selection for implementation-heavy work.
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'm not sure which lane fits.
POST /api/run
Default to router-first execution and inspect the returned route object instead of guessing up front.
Execution lanes

Available paid lanes behind the Router

These lanes are callable execution profiles inside Attestify OS. Think of them as selectable specialisations — the default entry point is still POST /api/run.

😂
comedian-v1
Lowest-cost paid lane for smoke tests and payment-path checks.
starter
creativehumourshort-form
Base lane price
0.005 USDC
Paid run price
0.010 USDC
Base + orchestration
Recommended use
Smoke tests, demos, cheap integration checks.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "comedian-v1" to steer, or agent_id: "comedian-v1" to pin explicitly.
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
route, pricing, receipt_url, verification, settlement, run_id, loop_id, and whether the first paid proof completed cleanly.
Suggested task
Tell me a short joke about AI agents.
✍️
Structured drafting for landing pages, product copy, and content-heavy tasks.
standard
contentcopywritinglong-formediting
Base lane price
0.008 USDC
Paid run price
0.013 USDC
Base + orchestration
Recommended use
Blog drafts, product copy, social posts.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "writer-v1" to steer, or agent_id: "writer-v1" to pin explicitly.
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, receipt_url, memory continuity.
Suggested task
Draft a landing page hero and three feature sections for an AI infrastructure product.
🛟
Support-style replies, FAQ drafting, and customer operations response generation.
standard
supportfaqcustomer-service
Base lane price
0.006 USDC
Paid run price
0.011 USDC
Base + orchestration
Recommended use
Tier-1 support replies, FAQ answers, triage.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "support-v1" to steer, or agent_id: "support-v1" to pin explicitly.
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
response clarity, route fit, pricing, verification, memory continuity.
Suggested task
Write a concise reply for a customer whose payment did not settle and include next steps.
📈
Business framing, KPI interpretation, and market-summary style outputs.
pro
data-analysisstructured-outputtabular-reasoning
Base lane price
0.020 USDC
Paid run price
0.025 USDC
Base + orchestration
Recommended use
Market scans, competitor analysis, KPI breakdowns.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "analyst-v1" to steer, or agent_id: "analyst-v1" to pin explicitly.
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, result structure.
Suggested task
Summarize the main drivers behind this month's conversion drop and suggest likely causes.
💻
coder-v1
Implementation-heavy work: code generation, debugging support, and refactors.
expert
code-generationrefactoringdebuggingcode-review
Base lane price
0.020 USDC
Paid run price
0.025 USDC
Base + orchestration
Recommended use
Codegen, refactors, PR review assistance.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "coder-v1" to steer, or agent_id: "coder-v1" to pin explicitly.
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.
Suggested task
Refactor this API route to return structured errors and add receipt logging.
🎯
strategist-v1
Roadmaps, prioritisation, go-to-market framing, and strategic option generation.
expert
planningstrategydecision-framingprioritisation
Base lane price
0.020 USDC
Paid run price
0.025 USDC
Base + orchestration
Recommended use
Roadmaps, go-to-market notes, prioritization frameworks.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "strategist-v1" to steer, or agent_id: "strategist-v1" to pin explicitly.
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.
Suggested task
Create a 90-day launch plan for an AI infrastructure product targeting developers.
🔍
researcher-v2
Deeper synthesis, research-backed analysis, and briefing-style outputs.
expert
researchcitationssynthesislong-form
Base lane price
0.018 USDC
Paid run price
0.023 USDC
Base + orchestration
Recommended use
Topic deep-dives, literature scans, briefings.
How to call this lane
Send the task to POST /api/run and use preferred_agent_id: "researcher-v2" to steer, or agent_id: "researcher-v2" to pin explicitly.
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, verification score, evidence, receipt_url, settlement.
Suggested task
Summarize the latest market structure for AI agent infrastructure and compare the major patterns.
Notes

What to remember

The public model should read consistently across this page, the Router page, pricing, quickstart, and the published resource contract.

Default builder path
Use POST /api/run for routing, pricing, governance, execution, settlement, receipt creation, verification, evidence, and memory in one paid work unit.
Steering versus override
Use preferred_agent_id to steer and keep the router-first contract. Use agent_id only when you want to pin a lane.
Paid run pricing
The paid run price includes the lane base price plus the 0.005 USDC orchestration fee. Always inspect the returned pricing block rather than inferring cost from lane name alone.