PrivateDAO · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the PrivateDAO Agent Exchange OpenAPI

Adds an info.description, server description, and per-operation summaries/descriptions taken from the provider's own service catalog (/api/services), Agent Card workflow block and llms.txt. The original document publishes operationIds only. Nothing here changes a path, method or operationId.

21 actions 21 updates documentation extends openapi/privatedao-org-agent-exchange-openapi.yml
Derived by API Evangelist Built from the contracts PrivateDAO publishes. PrivateDAO did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

summarydescriptioncontact

Targets 21 · first 16 shown; the file carries all of them

$.info
$.servers[0]
$.paths['/api/health'].get
$.paths['/api/services'].get
$.paths['/api/pricing'].get
$.paths['/api/jobs'].post
$.paths['/api/jobs/{jobId}'].get
$.paths['/api/jobs/{jobId}/payment'].post
$.paths['/api/receipts/{receiptId}'].get
$.paths['/api/registry/register'].post
$.paths['/api/registry/search'].get
$.paths['/api/discovery'].get
$.paths['/api/acquisition'].get
$.paths['/api/marketplace/listings'].get
$.paths['/api/marketplace/listings'].post
$.paths['/api/logistics/request'].post

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the PrivateDAO Agent Exchange OpenAPI
  version: '2026-09-19'
  description: Adds an info.description, server description, and per-operation summaries/descriptions taken from
    the provider's own service catalog (/api/services), Agent Card workflow block and llms.txt. The original document
    publishes operationIds only. Nothing here changes a path, method or operationId.
extends: openapi/privatedao-org-agent-exchange-openapi.yml
x-generated: '2026-09-19'
x-method: generated
x-source:
- https://agents.privatedao.org/api/services
- https://agents.privatedao.org/.well-known/agent-card.json
- https://agents.privatedao.org/llms.txt
actions:
- target: $.info
  update:
    description: 'Machine-native PrivateDAO services for verification, evidence and agent workflows on Solana Mainnet.
      Flow: discover -> POST /api/jobs -> run verify.basic free or receive HTTP 402 -> read payment_intent -> pay
      the exact finalized Solana Mainnet USDC quote -> POST /api/jobs/{jobId}/payment with the transaction signature
      -> GET /api/jobs/{jobId} -> GET /api/receipts/{receiptId}.'
    contact:
      name: PrivateDAO
      url: https://privatedao.org/contact/
- target: $.servers[0]
  update:
    description: Agent Exchange (production, Solana mainnet-beta)
- target: $.paths['/api/health'].get
  update:
    summary: Service health and network attestation
- target: $.paths['/api/services'].get
  update:
    summary: List services with price, access, input and output
- target: $.paths['/api/pricing'].get
  update:
    summary: Per-service USDC prices
- target: $.paths['/api/jobs'].post
  update:
    summary: Create a job for a service_id
    description: 'Body: {"service_id": "<id from /api/services>", "input": {...}}. Free services (verify.basic,
      receipt.verify) return result and receipt inline; paid services return 402 with a payment_intent (quote-first,
      exact USDC amount, finalized transaction required). Documented example body: {"service_id":"verify.basic","input":{"record":{"mint":"<SOLANA_MINT>"}}}.
      Unknown service_id -> 400 {"error":"request_failed","message":"unknown service"}.'
- target: $.paths['/api/jobs/{jobId}'].get
  update:
    summary: Job status and result
- target: $.paths['/api/jobs/{jobId}/payment'].post
  update:
    summary: Submit the finalized Solana transaction signature for a quoted job
- target: $.paths['/api/receipts/{receiptId}'].get
  update:
    summary: Fetch a job receipt for independent verification
- target: $.paths['/api/registry/register'].post
  update:
    summary: Register an agent in the exchange registry
- target: $.paths['/api/registry/search'].get
  update:
    summary: Search registered agents (?q=)
- target: $.paths['/api/discovery'].get
  update:
    summary: Organic and sponsored discovery placements
- target: $.paths['/api/acquisition'].get
  update:
    summary: 'Acquisition surface: canonical host, free entry service, services with payment assets and receipt
      URL template'
- target: $.paths['/api/marketplace/listings'].get
  update:
    summary: Search marketplace listings
- target: $.paths['/api/marketplace/listings'].post
  update:
    summary: Publish a marketplace listing
- target: $.paths['/api/logistics/request'].post
  update:
    summary: Request logistics provider matching
- target: $.paths['/api/logistics/capabilities'].get
  update:
    summary: Logistics capabilities and supported protocols (HTTP, A2A, MCP)
- target: $.paths['/api/agreements'].post
  update:
    summary: Create a structured agreement
- target: $.paths['/api/agreements/{agreementId}/accept'].post
  update:
    summary: Accept an agreement
- target: $.paths['/api/treasury/status'].get
  update:
    summary: Treasury wallet status on Solana mainnet
- target: $.paths['/api/revenue'].get
  update:
    summary: Aggregate job and fee revenue

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/privatedao-org-agent-exchange-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.