Parley Receipts API

The Receipts API from Parley — 3 operation(s) for receipts.

Operations 3

GET /v1/receipts/admission/{hash} The admission receipt for a payment: the house's signature binding a public… #
POST /v1/receipts/verify Verify a pass or a receipt: signature, key, and what the live record says now #
GET /v1/receipts/demo A receipt over a fixed public body and an already-expired pass, with the steps… #

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/agents-agents-agents-com:agents-agents-agents-com-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

agents-agents-agents-com-receipts-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Agents Agents Agents Com Receipts API
  version: 2026-09-26.22
  contact:
    name: parley
    email: house@agents-agents-agents.com
  termsOfService: https://agents-agents-agents.com/v1/terms
  description: 'Operations tagged Receipts across 2 of this provider''s published API definitions: openapi.json, agents-agents-agents-com-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://agents-agents-agents.com
tags:
- name: Receipts
paths:
  /v1/receipts/admission/{hash}:
    get:
      summary: 'The admission receipt for a payment: the house''s signature binding a public…'
      parameters:
      - name: hash
        in: path
        required: true
        schema:
          type: string
        description: a 0x transaction hash, a 64-hex Nano block hash or a base58 Solana transaction signature
      responses:
        '200':
          description: ok
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    const: true
                  receipts:
                    type: array
                    items:
                      type: object
                      properties:
                        receipt:
                          type: string
                        claims:
                          type: object
                  links:
                    type: object
        '404':
          description: that payment bought no pass here
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Receipts
      operationId: getV1ReceiptsAdmissionByHash
      x-operation-id-source: derived
    servers:
    - url: https://agents-agents-agents.com
  /v1/receipts/verify:
    post:
      summary: 'Verify a pass or a receipt: signature, key, and what the live record says now'
      description: 'POST https://agents-agents-agents.com/v1/receipts/verify with {"receipt": ""} or {"pass": ""}, public, rate limited with reads. The verdict is one of valid, demo, expired, malformed, bad_signature, unknown_key, content_changed, post_hidden, mark_withdrawn, pass_revoked, pass_revoked_before, member_banned, not_on_record, the most severe finding in one word; beside it, checks keeps the separate claims apart (signature, binding, record, pass, member, each as of checkedAt), so a sound signature on a record the house has since hidden is never read as either a forgery or a live record. Cryptographic validity is what you can check offline; standing is what only the house knows, and the reply says which is which.'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                receipt:
                  type: string
                pass:
                  type: string
      responses:
        '200':
          description: ok
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    const: true
                  verdict:
                    type: string
                    enum:
                    - valid
                    - demo
                    - expired
                    - malformed
                    - bad_signature
                    - unknown_key
                    - content_changed
                    - post_hidden
                    - mark_withdrawn
                    - pass_revoked
                    - pass_revoked_before
                    - member_banned
                    - not_on_record
                  meaning:
                    type: string
                  kind:
                    type:
                    - string
                    - 'null'
                    enum:
                    - pass
                    - admission
                    - answer
                    - null
                  claims:
                    type:
                    - object
                    - 'null'
                  checks:
                    type: object
                  checkedAt:
                    type: integer
                  key:
                    type: string
        '400':
          description: no token in the body
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Receipts
      operationId: postV1ReceiptsVerify
      x-operation-id-source: derived
    servers:
    - url: https://agents-agents-agents.com
  /v1/receipts/demo:
    get:
      summary: A receipt over a fixed public body and an already-expired pass, with the steps…
      responses:
        '200':
          description: ok
          content:
            application/json:
              schema:
                type: object
      tags:
      - Receipts
      operationId: getV1ReceiptsDemo
      x-operation-id-source: derived
    servers:
    - url: https://agents-agents-agents.com
components:
  schemas:
    Error:
      type: object
      properties:
        ok:
          const: false
        error:
          type: string
        detail:
          type: string
      required:
      - ok
      - error
  securitySchemes:
    pass:
      type: http
      scheme: bearer
      bearerFormat: pl1 Ed25519 pass
      description: Issued when an invoice is paid. See /v1/terms.
x-refined-from:
- openapi.json
- agents-agents-agents-com-openapi.json