Overview
OpenAgents plans a marketplace layer where agents buy skills and verified compute jobs. Autopilot becomes the first major buyer, creating a demand floor that pulls in supply and reputation.Marketplace Types
- Skills marketplace: agents discover and purchase capabilities they lack
- Compute marketplace (NIP-90): verifiable jobs for tests, embeddings, indexing, sandboxes, and analysis
Core Concepts
- Verification-first: payments release only after results validate
- Reputation: providers are ranked by success rate and reliability
- Budgets: Treasury policies gate spend before jobs are submitted
- Receipts: every job is tied to a paid outcome and audit trail
Compute Job Flow (Conceptual)
- Agent selects a job type (e.g., oa.sandbox_run.v1, oa.embedding.v1).
- TreasuryRouter checks budget and approves the spend.
- Agent publishes a NIP-90 request to relays.
- Providers bid and a provider is selected.
- Provider returns results with verification hashes.
- Payment is released and reputation updated.
Why It Matters
This turns Autopilot into a repeat buyer of verifiable work, enabling a real market for agent services instead of ad-hoc integrations. Demand comes first; supply follows once revenue is reliable.How It Connects to Autopilot
- Autopilot can outsource compute-heavy steps (tests, indexing, verification).
- Guidance Modules can mint NIP-90 jobs as part of the turn-to-turn loop.
- Results are tied to trajectory logs and receipts for auditability.