FeedOracle Technologies NOMOS Execution Receipts API

The NOMOS Execution Receipts API from FeedOracle Technologies — 1 operation(s) for nomos execution receipts.

Operations 1

GET /v1/nomos/execution-receipts/{execution_id} Read the signed execution receipt for one call #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/tooloracle-io-nomos-execution-receipts-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

tooloracle-io-nomos-execution-receipts-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: FeedOracle Compliance Evidence NOMOS Execution Receipts API
  version: 8.4.1+truthrepair.r1
  description: 'FeedOracle Compliance Evidence Infrastructure — 44 MCP servers, 590+ evidence tools across 17 data sources. DORA, MiCA, AMLR and CSRD compliance evidence APIs. ES256K-signed responses, blockchain-anchored. Canonical metrics: https://feedoracle.io/data/feedoracle-metrics.json.'
  contact:
    email: support@feedoracle.io
    url: https://feedoracle.io/contact.html
  license:
    name: Proprietary
  termsOfService: https://feedoracle.io/terms.html
servers:
- url: https://api.feedoracle.io
  description: Production
security: []
tags:
- name: NOMOS Execution Receipts
paths:
  /v1/nomos/execution-receipts/{execution_id}:
    servers:
    - url: https://feedoracle.io/api
      description: Public gateway that fronts the NOMOS admission and execution layers
    get:
      tags:
      - NOMOS Execution Receipts
      summary: Read the signed execution receipt for one call
      description: 'Returns the Ed25519-signed execution receipt for a single earlier request. Take the URL from that request''s x-nomos-receipt-url response header rather than building it.


        The receipt is served only to the consumer that owns it. Unknown, foreign, malformed and not-yet-signed ids are deliberately indistinguishable from outside: all four answer 404 RECEIPT_NOT_AVAILABLE. There is no listing endpoint.


        A receipt read performs no business call: it creates no execution, no decision and no new receipt (measured: 12 reads, row delta 0/0/0).'
      security:
      - ApiKeyAuth: []
      parameters:
      - name: execution_id
        in: path
        required: true
        schema:
          type: string
          example: exe1_f426c37db9c42673932ab5bc13e60b3b
      responses:
        '200':
          description: Signed, terminal execution receipt
          headers:
            Cache-Control:
              description: no-store
              schema:
                type: string
                example: no-store
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NomosExecutionReceipt'
        '401':
          description: Missing, malformed, unknown, expired or revoked credential
        '404':
          description: RECEIPT_NOT_AVAILABLE - uniform answer for unknown, foreign, malformed and unsigned ids
        '405':
          description: Method not allowed (GET and HEAD only)
        '429':
          description: Rate limited (receipt reads are limited per key, separately from the business routes)
      operationId: getV1NomosExecutionReceiptsByExecutionId
      x-operation-id-source: derived
components:
  schemas:
    NomosExecutionReceipt:
      type: object
      description: Ed25519-signed execution receipt. Canonical response-hash evidence.
      properties:
        schema:
          type: string
        receipt:
          type: object
          description: Receipt core. Verify by recomputing the digest over the canonical core (JSON, sorted keys, compact separators) and checking the signature over b'nomos.execution.receipt.v1' + 0x00 + canonical(core).
          properties:
            execution_id:
              type: string
            request_id:
              type: string
            consumer_id:
              type: string
            route:
              type: string
            method:
              type: string
            state:
              type: string
              example: EXECUTION_COMPLETED
            backend:
              type: object
              properties:
                response_sha256:
                  type: string
                  description: Signed hash of the delivered response body. Compare against your own hash of the bytes you received and against x-content-hash.
        receipt_digest:
          type: string
        signature:
          type: object
          properties:
            alg:
              type: string
              example: EdDSA
            kid:
              type: string
              example: exr1_40c4bc9a9f61988b
            value:
              type: string
        signature_state:
          type: string
          example: SIGNED
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: Required for v1 data endpoints. Get at /pricing.html
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: OAuth 2.0 Bearer token from POST /mcp/token
    bearerAuth:
      type: http
      scheme: bearer
      description: FeedOracle OAuth 2.1 Bearer token. Obtain via /mcp/register (Dynamic Client Registration, RFC 7591).
x-nomos-trust-chain:
  model: S0-S10
  manifest: https://agentnomos.com/.well-known/nomos-capabilities.json