generated: '2026-09-19'
method: derived
source: mcp/01mind-net-mcp-tools.json (live tools/list, 2026-09-19) and a2a/01mind-net-agent-card.json (live card) bound to openapi/01mind-net-openapi.json
surfaces:
  openapi:
    file: openapi/01mind-net-openapi.json
    url: https://01mind.net/openapi.json
    operations: 28
    gated: false
    note: >-
      22 of 28 operations carry an operationId. The six that do not — POST /execute/{listingId}, POST
      /sandbox/execute/{listingId}, GET/POST /document-templates and DELETE /document-templates/{templateId}
      — are exactly the operations the MCP tools and A2A skills map onto, so the crosswalk below binds those
      rows by method + path. overlays/01mind-net-openapi-overlay.yaml proposes operationIds for them.
  mcp:
  - url: https://01mind.net/mcp
    gated: false
    note: Anonymous tools/list returned 3 tools with inputSchemas on 2026-09-19. Paid calls are x402-gated at invocation, not at listing.
  graphql: null
  a2a:
    url: https://01mind.net/a2a
    card: a2a/01mind-net-agent-card.json
    gated: false
    protocol_version: 0.3.0
    skills: 10
    note: >-
      Every skill is invoked the same way — a message carrying a DataPart {"listingId": "<skill id>"} under
      the required a2a-x402 extension — and every skill id is a catalogue listingId, so each skill binds to
      the REST purchase-and-collect path rather than to a distinct operation.
crosswalk:
- tool: list_offerings
  surface: mcp
  category: catalogue
  rest:
  - getCatalogueMenu
  - listOpenVenueTasks
  - 'GET /document-templates (no operationId)'
  binding: composite
  confidence: medium
  note: >-
    A read-only composite. Its "catalogue" section corresponds to the listing menu GET /charon/menu
    (getCatalogueMenu) and the listing catalogue GET /charon that the spec's /execute description points at
    but does not declare; "venue" corresponds to GET /venue/tasks (listOpenVenueTasks); "documents"
    corresponds to the RenderDocumentInput schema plus GET /document-templates. No single REST operation
    returns the same envelope.
- tool: render_document
  surface: mcp
  category: document-generation
  rest:
  - 'POST /execute/{listingId} with listingId=render-document (no operationId)'
  - 'POST /sandbox/execute/{listingId} with listingId=render-document (no operationId; free dry run)'
  binding: rest
  confidence: high
  note: >-
    Same product, same limits, same free-allowance rule and the same description text as the REST route; the
    REST RenderDocumentInput schema is the real input contract (the MCP inputSchema declares only format,
    filename and walletAddress). Through MCP the x402 payment travels in-band; through REST the buyer pays at
    /purchase/{listingId} (documented in prose, absent from the spec) and collects at /execute with an EIP-191
    wallet proof.
- tool: save_document_template
  surface: mcp
  category: document-generation
  rest:
  - 'POST /document-templates (no operationId)'
  binding: rest
  confidence: high
  note: Requires X-API-Key on both surfaces; free and does not consume the document allowance.
- tool: render-document
  surface: a2a
  category: document-generation
  rest:
  - 'POST /execute/{listingId} with listingId=render-document (no operationId)'
  binding: rest
  confidence: high
- tool: email-send-action-api
  surface: a2a
  category: action
  rest:
  - 'POST /execute/{listingId} with listingId=email-send-action-api (no operationId)'
  binding: rest
  confidence: medium
  note: >-
    The /execute route is declared with the RenderDocumentInput request schema only; the email payload shape
    is not in the spec. Bound by listingId, not by a documented input contract.
- tool: legal-research-knowledge-api
  surface: a2a
  category: specialised-knowledge
  rest:
  - 'POST /execute/{listingId} with listingId=legal-research-knowledge-api (no operationId)'
  binding: rest
  confidence: medium
  note: Same caveat — the question payload is undocumented in the spec.
- tool: agent-economy-venue-intelligence
  surface: a2a
  category: specialised-knowledge
  rest:
  - 'POST /execute/{listingId} with listingId=agent-economy-venue-intelligence (no operationId)'
  - 'GET /venue-intelligence/quick-check (free single-venue summary; live 200, absent from the spec)'
  binding: rest
  confidence: medium
- tool: au-tax-compliance-pack | gdpr-compliance-pack | hipaa-compliance-pack | asic-accc-guidance-pack | aviation-safety-pack
  surface: a2a
  category: reference-pack
  rest:
  - 'POST /execute/{listingId} with the pack id as listingId (no operationId)'
  binding: rest
  confidence: medium
  note: Five pre-generated reference documents; one purchase, collectable again by the paying wallet at no further charge (Terms of Sale 5.3).
- tool: pub_9a615b4fed78
  surface: a2a
  category: specialised-knowledge
  rest: []
  binding: none
  confidence: low
  note: >-
    Machine-named skill with an editorial-note description; it does not appear on the human catalogue page
    and no REST listing of that id was confirmed. Left unbound rather than guessed.
mcp_only: []
rest_only:
- capability: tool-generation-engine
  operations: [submitToolGenerationRequest, getToolGenerationRequest, replyToToolGenerationApproval, reportToolProductionFault, listCatalogueAdditions, getToolGenerationFaultLog, getToolRequestFormatGuide]
- capability: marketing-campaigns (internal, X-Console-Secret, never issued to customers)
  operations: [startMarketingCampaign, getMarketingCampaign, spendCampaignTokens, pauseCampaignForFault, resumeCampaignAfterFaultVerifiedFixed, completeCampaign, attachTopUpToCampaign, requestTokenTopUp, replyToTokenTopUp]
- capability: live-research-venue
  operations: [getVenueTask, applyToVenueTask, closeResearchTask, getResearchWelcome, converseWithResearch]
- capability: document-templates
  operations: ['DELETE /document-templates/{templateId} (no operationId)']
coverage:
  mcp_tools_named: 3
  mcp_tools_bound: 3
  a2a_skills_named: 10
  a2a_skills_bound: 9
  mcp_only: 0
  rest_operations_total: 28
  rest_operations_with_a_tool_or_skill: 5
  note: >-
    The agent surfaces cover the commerce path (browse, dry-run, execute, template) and nothing else; the
    tool-generation engine, the research venue's write operations and the internal campaign endpoints are
    REST-only. A2A skill coverage is 9 of 10 because pub_9a615b4fed78 could not be tied to a confirmed listing.