> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcenpay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Submit a zkTLS proof

> Verifies a Reclaim Protocol proof and attaches its claims to a company's traits. Replay-protected.



## OpenAPI

````yaml /openapi.yaml post /proofs/zktls
openapi: 3.0.3
info:
  title: ArcenPay API
  description: >
    The ArcenPay REST API powers subscription billing, entitlements, usage
    metering,

    payment links, checkout sessions, and autonomous agent payments across EVM
    (BOT Chain,

    Base, Arc, Sepolia) and Stellar.


    Every endpoint that accepts an API key supports the `Authorization: Bearer
    <key>` header.

    Key prefixes: `sk_…` (secret), `rk_…` (restricted), `pk_…` (publishable,
    read-only),

    `api_…` (legacy). Company-scoped customer endpoints accept an embed access
    token

    (`arc_tok_…` or a signed JWT from `identify()`). See the Authentication page
    for the

    full endpoint auth matrix.


    Manage catalog, environments, invoices, webhooks, feature flags, and agent
    configuration

    from the *dashboard* — those are not part of the developer-facing API
    reference.
  version: 1.0.0
servers:
  - url: https://api.arcenpay.com/api/v1
    description: Production
  - url: http://localhost:3300/api/v1
    description: Local development
security:
  - bearerAuth: []
tags:
  - name: Credentials
    description: >-
      API keys, secret/publishable/restricted credentials, and short-lived
      tokens.
  - name: Companies
    description: Customer organizations, identity synchronization, and feature overrides.
  - name: Users
    description: Customer end-users associated with company organizations.
  - name: Events
    description: Ingest customer usage events and identification signals.
  - name: Access control
    description: >-
      Real-time entitlement checks, feature flags, and metered credit
      consumption.
  - name: Subscriptions
    description: >-
      On-chain subscription activation, self-serve plan switching, proration,
      and cancellation.
  - name: Checkout sessions
    description: Hosted checkout session lifecycle and status lookup.
  - name: Payment links
    description: Crypto payment links and dynamic payment URLs.
  - name: Autonomous agents
    description: >-
      Agent permissions, budget checking, on-chain funding, and auto-topup
      dispatch.
  - name: Mandates
    description: Recurring billing authorizations and mandate lifecycle.
  - name: Coupons
    description: Discount code validation and proration quoting.
  - name: zkTLS proofs
    description: Zero-knowledge TLS proofs verification via Reclaim Protocol.
  - name: Public
    description: Unauthenticated payment link specifications and checkout sessions.
  - name: Escrow
    description: >-
      Autonomous commit-reveal escrow reservations, release settlement, and
      dispute handling.
  - name: Features
    description: Feature catalog definitions, feature types, and linked plan entitlements.
paths:
  /proofs/zktls:
    post:
      tags:
        - zkTLS proofs
      summary: Submit a zkTLS proof
      description: >-
        Verifies a Reclaim Protocol proof and attaches its claims to a company's
        traits. Replay-protected.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - proof
              properties:
                proof:
                  type: object
                  description: Reclaim proof with providerId and claimData.
                companyKeys:
                  type: object
                  properties:
                    id:
                      type: string
                    wallet:
                      type: string
                    email:
                      type: string
                userKeys:
                  type: object
                  properties:
                    id:
                      type: string
                    wallet:
                      type: string
                    email:
                      type: string
                expiresIn:
                  type: integer
                  description: Proof lifetime in seconds. 0 = no expiry.
      responses:
        '200':
          description: Proof verified and stored
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      id:
                        type: string
                      providerId:
                        type: string
                      claims:
                        type: object
                      companyId:
                        type: string
                        nullable: true
        '409':
          $ref: '#/components/responses/Conflict'
        '422':
          description: Proof verification failed.
      security:
        - bearerAuth: []
components:
  responses:
    Conflict:
      description: >-
        The request conflicts with current state (duplicate wallet, existing
        key, replay, etc.).
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
              code:
                type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: sk_… / rk_… / pk_… / api_…

````