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

# Verify a result token

> Validates a BotShield attestation JWT — the primary server-side check. Attestations are ES256-signed; the public key is published at /.well-known/jwks.json (kid in the header), so you may also verify locally with any JWT library. Claims are anonymous by construction: the token attests the event, never the person.



## OpenAPI

````yaml /openapi.json post /sdk/verify-token
openapi: 3.1.0
info:
  title: BotShield API
  version: 2.0.0
  description: >-
    The BotShield partner API.


    **BotShield Gate** — ask whether a live human is present (Human Gate) or
    over an age threshold (Age Gate). The person confirms with their device
    biometric in the BotShield app and you receive a signed result. Partners
    learn *that* a user is human, never *who*.


    **Agents Ask** — your agent proposes an action, a verified human confirms or
    denies it, and BotShield signs a Proof of Resolution you can verify offline.


    Every operation answers HTTP 200 with a `data` envelope; handler errors
    arrive as `data.error`. See the API overview and error reference. In the
    `botshield-sdk` package these operations live under `client.census.*`,
    `client.verification.*` and `client.actions.*`.
  contact:
    name: BotShield Support
    email: support@botshield.ai
    url: https://botshield.ai
servers:
  - url: https://api.botshield.ai/operations
    description: Production
security: []
tags:
  - name: BotShield Gate
    description: >-
      Place a gate and learn whether a present human (Human Gate) or a human
      over an age threshold (Age Gate) confirmed.
  - name: Agents Ask
    description: >-
      Your agent proposes an action; a verified human confirms or denies it in
      the BotShield app; you receive a signed Proof of Resolution.
paths:
  /sdk/verify-token:
    post:
      tags:
        - BotShield Gate
      summary: Verify a result token
      description: >-
        Validates a BotShield attestation JWT — the primary server-side check.
        Attestations are ES256-signed; the public key is published at
        /.well-known/jwks.json (kid in the header), so you may also verify
        locally with any JWT library. Claims are anonymous by construction: the
        token attests the event, never the person.
      operationId: SdkVerifyToken
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - token
              properties:
                token:
                  type: string
                  description: JWT verification receipt
      responses:
        '200':
          description: >-
            Validation result. NOTE: handler errors also arrive here (HTTP 200)
            as data.error — codes for this operation: none — an invalid token is
            a normal result with valid=false.
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                properties:
                  data:
                    type: object
                    properties:
                      data:
                        type: object
                        required:
                          - valid
                        properties:
                          valid:
                            type: boolean
                          reason:
                            type: string
                            description: Present when valid is false.
                          expired_at:
                            type: string
                            format: date-time
                            nullable: true
                            description: Present when the token was valid but has expired.
                          claims:
                            type: object
                            nullable: true
                            properties:
                              request_id:
                                type: string
                              verified:
                                type: boolean
                              organization_id:
                                type: string
                              timestamp:
                                type: string
                              nonce:
                                type: string
                              issued_at:
                                type: number
                              expires_at:
                                type: number
                      error:
                        $ref: '#/components/schemas/ErrorBody'
        '400':
          $ref: '#/components/responses/BadRequest'
        '500':
          $ref: '#/components/responses/InternalError'
components:
  schemas:
    ErrorBody:
      type: object
      required:
        - message
        - statusCode
      description: >-
        Handler error. Arrives inside data.error with HTTP 200 — check for it
        before reading the result.
      properties:
        message:
          type: string
        statusCode:
          type: integer
          description: >-
            The HTTP status the error stands for (401, 403, 404, 409, 422, 500,
            502).
        code:
          type: string
          description: Machine code when present, e.g. ttl_below_floor, ttl_above_ceiling.
        min_ttl_seconds:
          type: integer
        max_ttl_seconds:
          type: integer
        violations:
          type: array
          items:
            type: object
            properties:
              type:
                type: string
              path:
                type: string
              severity:
                type: string
          description: Adaptive Card TRUST-layer rejections (statusCode 422).
    InvalidInputError:
      type: object
      required:
        - message
        - input
        - errors
      properties:
        message:
          type: string
          example: Invalid input provided
        input:
          type: object
          additionalProperties: true
        errors:
          type: array
          items:
            type: object
            required:
              - propertyPath
              - invalidValue
              - message
            properties:
              propertyPath:
                type: string
              invalidValue:
                description: The invalid value
              message:
                type: string
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - message
            - statusCode
          properties:
            message:
              type: string
            statusCode:
              type: integer
  responses:
    BadRequest:
      description: Invalid input
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/InvalidInputError'
    InternalError:
      description: Internal server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'

````