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

# Start Registration

> Issue a single-use, short-lived nonce the agent must embed in its registration evidence, and `aud`, the platform DID  
The key being registered signs both in its `proof`, so a captured attestation cannot be replayed to bind a key the attacker never controlled  
The nonce is bound to your organization: it cannot be spent registering an agent elsewhere



## OpenAPI

````yaml /versions/2026-10-16.yaml post /agents/register-challenge
openapi: 3.1.0
info:
  title: Humanos API
  description: Humanos API
  version: '1.0'
  contact: {}
servers:
  - url: https://api.humanos.tech
security: []
tags:
  - name: humanosApp
    description: ''
paths:
  /agents/register-challenge:
    post:
      tags:
        - Agents
      summary: Start Registration
      description: >-
        Issue a single-use, short-lived nonce the agent must embed in its
        registration evidence, and `aud`, the platform DID  

        The key being registered signs both in its `proof`, so a captured
        attestation cannot be replayed to bind a key the attacker never
        controlled  

        The nonce is bound to your organization: it cannot be spent registering
        an agent elsewhere
      operationId: agents_registerChallenge
      parameters:
        - $ref: '#/components/parameters/ApiVersion'
      responses:
        '201':
          description: >-
            Returns the single-use nonce, its expiry and the audience the proof
            must name.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AgentChallengeEntity'
components:
  parameters:
    ApiVersion:
      name: API-Version
      in: header
      required: false
      schema:
        type: string
        pattern: ^\d{4}-\d{2}-\d{2}$
        example: '2026-10-16'
      description: >-
        Pin request, response, and webhook shapes to a specific dated API
        version (YYYY-MM-DD). Omit to use the version pinned to your API key
        (set when the key is created; new keys default to the latest version).
        New integrations should target the latest version.
  schemas:
    AgentChallengeEntity:
      type: object
      properties:
        regNonce:
          type: string
          description: Single-use nonce the registration evidence must embed.
          example: k3Jd0Q7bXm2sVQ8hZ1pYt4Rc
        exp:
          type: number
          description: Absolute expiry, epoch milliseconds.
          example: 1767225600000
        ttl:
          type: number
          description: Freshness window in seconds.
          example: 60
        aud:
          type: string
          description: >-
            The platform's DID: the `aud` a registration `proof` names. The key
            being registered signs a `via-reg+jwt` over this and the nonce (v0.3
            §16.5).
          example: did:web:humanos.tech
      required:
        - regNonce
        - exp
        - ttl
        - aud

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.