AlgoVoi Verify API

The Verify API from AlgoVoi — 6 operation(s) for verify.

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /verify Verify an audit bundle · Verify #
Ask an LLM
“How do I check an audit bundle's integrity without storing it anywhere?”
“Can the audit bundle signature be verified too?”
Tell an agent
Verify this audit bundle.
Check my audit bundle, including its signature with the supplied key.
POST /verify/rfc9421 Verify a signed HTTP message offline · Verify #
Ask an LLM
“Can I verify an HTTP message signature against the key I expect the signer to hold?”
“Does the free signature verifier error out on a bad signature, or return valid false?”
Tell an agent
Verify this signed message envelope against my expected key.
Check offline whether this RFC 9421 signed request is valid.
GET /verify/rfc9421 Get the RFC 9421 verifier's input schema · RFC 9421 verifier — schema and spec reference #
Ask an LLM
“What input does the free RFC 9421 verifier expect?”
“Which spec does the HTTP message signature verifier implement?”
Tell an agent
Show the RFC 9421 verifier input schema.
Get the spec reference for the HTTP signature verifier.
POST /verify/rfc9421/explain Explain why an HTTP signature passes or fails · Explain #
Ask an LLM
“Why is my RFC 9421 signature failing, and how do I fix it?”
“Can I see the exact canonical signing base the verifier computed?”
Tell an agent
Explain why this signed request fails and show the signing base.
Debug my message signature and give how-to-fix notes.
POST /verify/rfc9421/sign Sign a sample request with a demo key · Sign Demo #
Ask an LLM
“Is there a reference signer I can diff my own RFC 9421 signer against?”
“Do I need to send a private key to get a correctly signed example?”
Tell an agent
Sign these request inputs with a throwaway demo key.
Produce a known-good signed request and signing base for comparison.
POST /v1/verify Verify an MPP on-chain payment transaction · MPP payment verification #
Ask an LLM
“How does the MPP adapter confirm a payer's on-chain transaction?”
“What does the gateway return when an MPP payment checks out, a receipt JWT?”
Tell an agent
Verify tx {tx_id} on {network} for resource {resource_id}.
Confirm MPP payment {tx_id} for {resource_id} and return the receipt.
GET /verify/action-ref Get the action_ref verifier's input schema · action_ref verifier — schema and spec reference #
Ask an LLM
“What fields does the action_ref verifier take?”
“Where is the spec reference for computing an action_ref?”
Tell an agent
Show the action_ref verifier schema.
Get the spec reference for action_ref hashing.
POST /verify/action-ref Compute the canonical action_ref hash · Compute and verify an action_ref canonical hash #
Ask an LLM
“How do I check my implementation computes the same action_ref hash as production?”
“What canonical form is the action_ref hashed from?”
Tell an agent
Compute the action_ref for agent {agent_id}, action {action_type}, scope {scope} at {timestamp_ms}.
Hash action {action_type} by {agent_id} with scope {scope} at {timestamp_ms} ms.

Documentation

Specifications

Other Resources

🔗
AgentCard
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/a2a/algovoi-co-uk-a2a.yml
🔗
AgentCard
https://pay.algovoi.co.uk/.well-known/agent-card.json
🔗
LLMsTxt
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/llms/algovoi-co-uk-pay-llms.txt
🔗
LLMsTxt
https://pay.algovoi.co.uk/llms.txt
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/conventions/algovoi-co-uk-conventions.yml
🔗
Idempotency
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/conventions/algovoi-co-uk-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/errors/algovoi-co-uk-problem-types.yml
🔗
Plans
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/plans/algovoi-co-uk-plans-pricing.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/sandbox/algovoi-co-uk-sandbox.yml
🔗
ErrorCodes
https://docs.algovoi.co.uk/api-reference/errors
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/asyncapi/algovoi-co-uk-webhooks.yml
🔗
Webhooks
https://docs.algovoi.co.uk/integrations/outbound-webhooks
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/data-model/algovoi-co-uk-data-model.yml
🔗
AgentCard
https://api.algovoi.co.uk/.well-known/agent-card.json
🔗
SignUp
https://dash.algovoi.co.uk/signup
🔗
Components
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/components/algovoi-co-uk-components.yml
🔗
AgentCard
https://agents.algovoi.co.uk/.well-known/agent-card.json
🔗
LLMsTxt
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/llms/algovoi-co-uk-clinic-llms.txt
🔗
LLMsTxt
https://agents.algovoi.co.uk/llms.txt
🔗
Dashboard
https://agent-trust-bench.algovoi.co.uk/stats
🔗
SourceCode
https://github.com/chopmob-cloud/algovoi-audit-verifier
🔗
ToolCrosswalk
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/mcp/algovoi-co-uk-tool-crosswalk.yml
🔗
SourceCode
https://github.com/chopmob-cloud/AlgoVoi-MCP-Server
🔗
Packages
https://raw.githubusercontent.com/api-evangelist/algovoi-co-uk/refs/heads/main/packages/algovoi-co-uk-packages.yml

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/algovoi-co-uk:algovoi-co-uk-verify-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

algovoi-co-uk-verify-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Algovoi Co Uk Verify API
  x-refined-note:
  - x-guidance differs across the merged source definitions and was not carried
  version: '1.0'
  description: 'Operations tagged Verify across 3 of this provider''s published API definitions: algovoi-co-uk-audit-verifier-openapi.json, algovoi-co-uk-clinic-openapi.json, algovoi-co-uk-gateway-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Verify
paths:
  /verify:
    post:
      summary: Verify
      description: 'Verify an audit bundle.


        The request body MUST be JSON. The bundle is verified in-memory and the

        result is returned; nothing is persisted. If the bundle is signed and

        you want bundle_signature verified, pass the signing key in the

        `X-Audit-Bundle-Key` header; otherwise the signature step is skipped

        (the structural checks 1 and 2 still run).'
      operationId: verify_verify_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Verify
  /verify/rfc9421:
    post:
      summary: Verify
      description: 'Verify a signed message offline. Caller supplies the envelope + the key they

        EXPECT the signer to hold (anchoring). Returns valid/errors -- never throws on a

        verification failure, only on a malformed request.'
      operationId: verify_verify_rfc9421_post
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              type: object
              title: Payload
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Verify Verify Rfc9421 Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Verify
    get:
      tags:
      - Verify
      summary: RFC 9421 verifier — schema and spec reference
      description: Return the input schema and spec reference for the RFC 9421 verifier.
      operationId: rfc9421_info_verify_rfc9421_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      x-payment-info:
        authMode: api_key
  /verify/rfc9421/explain:
    post:
      summary: Explain
      description: 'Debug a signed message: pass/fail PLUS why -- the exact canonical signing base, covered components,

        params, a Content-Digest recomputation, and human ''how to fix'' notes. Free. This is the #1 thing agent

        builders asked us to ship. public_key_hex/did_key is optional; without it you still get the signing base.'
      operationId: explain_verify_rfc9421_explain_post
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              type: object
              title: Payload
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Explain Verify Rfc9421 Explain Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Verify
  /verify/rfc9421/sign:
    post:
      summary: Sign Demo
      description: 'Known-good signer/playground: give raw request inputs, get a correctly-signed request + the

        signing base + an EPHEMERAL demo key to verify it with. NEVER send a private key — it signs with a

        fresh throwaway key so you can diff your own signer against a reference. Free.'
      operationId: sign_demo_verify_rfc9421_sign_post
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: true
              type: object
              title: Payload
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Sign Demo Verify Rfc9421 Sign Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Verify
  /v1/verify:
    post:
      tags:
      - Verify
      summary: MPP payment verification
      description: 'Verify an on-chain payment transaction for the MPP adapter.


        The adapter submits the tx_id and network from the payer''s credential;

        the gateway looks up the resource definition to get the expected amount

        and receiver, then delegates to the facilitator for on-chain confirmation.


        Returns a receipt JWT on success.'
      operationId: mpp_verify_v1_verify_post
      parameters:
      - name: tenant_id
        in: query
        required: false
        schema:
          anyOf:
          - type: string
            format: uuid
          - type: 'null'
          title: Tenant Id
      - name: x-tenant-id
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Tenant-Id
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/MppVerifyRequest'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MppVerifyResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      x-payment-info:
        authMode: api_key
  /verify/action-ref:
    get:
      tags:
      - Verify
      summary: action_ref verifier — schema and spec reference
      description: Return the input schema and spec reference for the action_ref verifier.
      operationId: action_ref_info_verify_action_ref_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      x-payment-info:
        authMode: api_key
    post:
      tags:
      - Verify
      summary: Compute and verify an action_ref canonical hash
      description: 'Compute the canonical action_ref for the supplied payload.


        The canonical form is RFC 8785 JCS (keys sorted, no whitespace).

        The action_ref is SHA-256(canonical_bytes), lowercase hex.


        This is the same computation the AlgoVoi production stack applies

        before issuing a compliance receipt — any implementation that

        produces a different hash for the same input is non-conformant.'
      operationId: verify_action_ref_verify_action_ref_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ActionRefRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ActionRefResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      x-payment-info:
        authMode: api_key
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    ValidationError_2:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    MppVerifyResponse:
      properties:
        verified:
          type: boolean
          title: Verified
        payer:
          type: string
          title: Payer
          default: ''
        amount:
          type: integer
          title: Amount
          default: 0
        receipt:
          type: string
          title: Receipt
          default: ''
        error:
          anyOf:
          - type: string
          - type: 'null'
          title: Error
      type: object
      required:
      - verified
      title: MppVerifyResponse
    MppVerifyRequest:
      properties:
        tx_id:
          type: string
          title: Tx Id
        network:
          type: string
          title: Network
        resource_id:
          type: string
          title: Resource Id
        tenant_id:
          anyOf:
          - type: string
          - type: 'null'
          title: Tenant Id
      type: object
      required:
      - tx_id
      - network
      - resource_id
      title: MppVerifyRequest
    Rfc9421VerifyResponse:
      properties:
        valid:
          type: boolean
          title: Valid
        signature_valid:
          type: boolean
          title: Signature Valid
        content_digest_valid:
          type: boolean
          title: Content Digest Valid
        signing_base:
          type: string
          title: Signing Base
        covered_components:
          items:
            type: string
          type: array
          title: Covered Components
        parameters:
          additionalProperties: true
          type: object
          title: Parameters
        label:
          type: string
          title: Label
        errors:
          items:
            type: string
          type: array
          title: Errors
        spec_ref:
          type: string
          title: Spec Ref
        digest_spec_ref:
          type: string
          title: Digest Spec Ref
      type: object
      required:
      - valid
      - signature_valid
      - content_digest_valid
      - signing_base
      - covered_components
      - parameters
      - label
      - errors
      - spec_ref
      - digest_spec_ref
      title: Rfc9421VerifyResponse
    ActionRefResponse:
      properties:
        action_ref:
          type: string
          title: Action Ref
        canonical_json:
          type: string
          title: Canonical Json
        sha256_hex:
          type: string
          title: Sha256 Hex
        spec_ref:
          type: string
          title: Spec Ref
        canonicalization:
          type: string
          title: Canonicalization
        implementations_attested:
          type: integer
          title: Implementations Attested
        attestation_ref:
          type: string
          title: Attestation Ref
      type: object
      required:
      - action_ref
      - canonical_json
      - sha256_hex
      - spec_ref
      - canonicalization
      - implementations_attested
      - attestation_ref
      title: ActionRefResponse
    ValidationError_3:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    Rfc9421VerifyRequest:
      properties:
        method:
          type: string
          title: Method
          description: HTTP method (e.g. POST)
        authority:
          type: string
          title: Authority
          description: HTTP authority (host[:port])
        path:
          type: string
          title: Path
          description: Request path + query (e.g. /checkout?token=abc)
        scheme:
          type: string
          title: Scheme
          description: URI scheme
          default: https
        headers:
          additionalProperties:
            type: string
          type: object
          title: Headers
          description: All HTTP headers as a flat dict (lowercase keys). Must include 'signature-input' and 'signature'. Include 'content-digest' when require_content_digest=true.
        body_b64:
          type: string
          title: Body B64
          description: Request body, base64-encoded. Empty string for requests with no body.
          default: ''
        public_key_hex:
          type: string
          title: Public Key Hex
          description: Ed25519 public key as 64-char hex (32 bytes). Must match the keyid used when signing.
        require_content_digest:
          type: boolean
          title: Require Content Digest
          description: If true, verify Content-Digest header against the body. Set false for GET/HEAD requests.
          default: true
        mode:
          type: string
          title: Mode
          description: '''rfc9421'' (default) for RFC 9421 §2.5 compliant signing base. ''algovoi-v0'' for legacy format used in rfc9421_proxy_chain_v0 conformance vectors.'
          default: rfc9421
      type: object
      required:
      - method
      - authority
      - path
      - headers
      - public_key_hex
      title: Rfc9421VerifyRequest
    ActionRefRequest:
      properties:
        agent_id:
          type: string
          title: Agent Id
          description: DID or URL identifying the agent (e.g. did:web:api.example.com)
        action_type:
          type: string
          title: Action Type
          description: Dot-namespaced action class (e.g. payment.authorize)
        scope:
          type: string
          title: Scope
          description: Chain-scoped target (e.g. base:0xabc...)
        timestamp_ms:
          type: integer
          title: Timestamp Ms
          description: Unix timestamp in integer milliseconds — NOT float
      type: object
      required:
      - agent_id
      - action_type
      - scope
      - timestamp_ms
      title: ActionRefRequest
x-refined-from:
- algovoi-co-uk-audit-verifier-openapi.json
- algovoi-co-uk-clinic-openapi.json
- algovoi-co-uk-gateway-openapi.json