Vaultfire Protocol · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Vaultfire Agent Hub API

7 actions 7 updates security extends ./theloopbreaker-com-openapi.yml
Derived by API Evangelist Built from the contracts Vaultfire Protocol publishes. Vaultfire Protocol did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

responsesx-reversibilityx-llms-txtx-agent-cardx-x402-manifestx-release-statussecuritySchemesheaders

Targets 7

$.info
$.components
$.paths['/agent/route'].post
$.paths['/agent/status'].get
$.paths['/agent/webhooks'].post
$.paths['/agent/register'].post
$.paths['/agent/bond'].post

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Vaultfire Agent Hub API
  version: 1.0.0
  x-generated: '2026-09-19'
  x-method: derived
  x-source: >-
    Observed behaviour from live 2026-09-19 probes of https://theloopbreaker.com/api and the provider's own
    llms.txt; the original contract at openapi/theloopbreaker-com-openapi.yml (verbatim copy in
    openapi/_original/) is not modified. This overlay records what the served spec leaves out — the ERC-8128
    signature requirement, the observed 4xx/5xx shapes, the documented rate-limit headers — so a consumer
    applying it gets a contract closer to the wire.
extends: ./theloopbreaker-com-openapi.yml
actions:
  - target: $.info
    description: Point at the provider's own agent-facing documentation and the discovery graph.
    update:
      x-llms-txt: https://theloopbreaker.com/llms.txt
      x-agent-card: https://theloopbreaker.com/.well-known/agent-card.json
      x-x402-manifest: https://theloopbreaker.com/.well-known/x402.json
      x-release-status: https://theloopbreaker.com/.well-known/release-status.json
  - target: $.components
    description: Declare the signature scheme the live API enforces on routing writes (observed 401 "unsigned").
    update:
      securitySchemes:
        erc8128HttpSignature:
          type: http
          scheme: signature
          description: >-
            ERC-8128 signed HTTP request — Signature and Signature-Input headers (RFC 9421 profile) signed by
            the sender wallet. Observed required on POST /agent/route; the served spec declares no security.
      responses:
        BadRequest:
          description: Missing or invalid required parameter (observed)
          content:
            application/json:
              schema: {type: object, properties: {error: {type: string}}, required: [error]}
              example: {error: 'Missing required query param: address'}
        Unsigned:
          description: Request lacks ERC-8128 Signature / Signature-Input headers (observed)
          content:
            application/json:
              schema: {type: object, properties: {error: {type: string}, reason: {type: string}}, required: [error]}
              example: {error: unsigned, reason: Request is missing ERC-8128 Signature and/or Signature-Input headers}
        RateLimited:
          description: Rate limit exceeded — 120 requests/minute per llms.txt (documented, not observed)
          headers:
            Retry-After: {schema: {type: integer}, description: seconds to wait}
        NotConfigured:
          description: Feature switched off server-side (observed on webhook registration)
          content:
            application/json:
              schema: {type: object, properties: {error: {type: string}, code: {type: string}}, required: [error, code]}
              example: {error: webhook write service is not configured, code: webhook_auth_unconfigured}
      headers:
        X-RateLimit-Limit: {schema: {type: integer}, description: requests per minute (documented value 120)}
        X-RateLimit-Remaining: {schema: {type: integer}}
        X-RateLimit-Reset: {schema: {type: integer}, description: Unix timestamp when the window resets}
  - target: $.paths['/agent/route'].post
    description: Attach the observed security requirement and the observed 401.
    update:
      security: [{erc8128HttpSignature: []}]
      responses:
        '400': {$ref: '#/components/responses/BadRequest'}
        '401': {$ref: '#/components/responses/Unsigned'}
        '429': {$ref: '#/components/responses/RateLimited'}
  - target: $.paths['/agent/status'].get
    update:
      responses:
        '400': {$ref: '#/components/responses/BadRequest'}
        '429': {$ref: '#/components/responses/RateLimited'}
  - target: $.paths['/agent/webhooks'].post
    update:
      responses:
        '503': {$ref: '#/components/responses/NotConfigured'}
        '429': {$ref: '#/components/responses/RateLimited'}
  - target: $.paths['/agent/register'].post
    description: State the custody model the response description implies.
    update:
      x-reversibility: none once the returned transaction is signed and broadcast (Terms section 3); the API call itself mutates nothing.
  - target: $.paths['/agent/bond'].post
    update:
      x-reversibility: none by the caller; bond distribution/return is contract logic (see conventions/).

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/theloopbreaker-com-openapi-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.