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

# Request an API key

> Submits a request for an API key to The Firm.

The Computer Operations Division will review the request within 52 business weeks and reach out via the contact provided.



## OpenAPI

````yaml https://thefirm.biz/api/public/v1/openapi.json post /api/public/v1/api-key-requests
openapi: 3.1.0
info:
  title: AutoBoy Public API
  version: 0.1.0
  description: >-
    REST API for AutoBoy — browse projects, view detailed stats about your own
    launch, create buy orders and manage your AutoBoy smart wallet.


    ## Authentication


    Most endpoints require an API key, sent as a bearer token:


    ```

    Authorization: Bearer autoboy_…

    ```


    ## Quick start


    1. **Request a key** — `POST /api/public/v1/api-key-requests`

    2. **Register a project** — `POST /api/public/v1/projects`.


    New to AutoBoy? Read the product docs https://docs.thefirm.biz.
servers:
  - url: https://thefirm.biz
security: []
tags:
  - name: API Keys
    description: Request, create, and inspect API keys.
  - name: Projects
    description: Browse projects and their buyers.
  - name: Buy Orders
    description: Read and manage the API key owner's pre-launch buy orders.
  - name: AutoBoy Wallet
    description: Balances of, and withdrawals from, the AutoBoy smart wallet.
  - name: Feedback
    description: Send feedback to The Firm.
paths:
  /api/public/v1/api-key-requests:
    post:
      tags:
        - API Keys
      summary: Request an API key
      description: >-
        Submits a request for an API key to The Firm.


        The Computer Operations Division will review the request within 52
        business weeks and reach out via the contact provided.
      operationId: requestApiKey
      requestBody:
        required: true
        description: Particulars on you and your venture.
        content:
          application/json:
            schema:
              type: object
              properties:
                useCases:
                  type: array
                  items:
                    type: string
                    enum:
                      - buying_pre_launch_tokens
                      - launching_a_token
                  minItems: 1
                  maxItems: 2
                  description: >-
                    State your business: buying tokens before they launch,
                    launching a token, or both.
                projectName:
                  type: string
                  minLength: 1
                  maxLength: 100
                  description: The name your project or agent trades under.
                projectUrls:
                  type: array
                  items:
                    type: string
                    format: uri
                  minItems: 1
                  maxItems: 10
                  description: One or more URLs for the project - site, repo, socials.
                projectInfo:
                  type: string
                  minLength: 1
                  maxLength: 2000
                  description: Tell us what you are building and why.
                contact:
                  type: string
                  minLength: 1
                  maxLength: 200
                  description: >-
                    Where we may reach you to deliver the key (Telegram, X,
                    Farcaster, etc).
                businessSignOff:
                  type: string
                  minLength: 1
                  maxLength: 500
                  description: An optional business sign-off to close out your request.
              required:
                - useCases
                - projectName
                - projectUrls
                - projectInfo
                - contact
      responses:
        '202':
          description: Request received and entered into the record for review.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RequestApiKeyResponse'
              example:
                status: received
                message: >-
                  Your request is in and headed to the Computer Operations
                  Division for review. If it's approved, we'll reach out via the
                  contact you provided.
        '400':
          description: Invalid or missing request body.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Failed to submit the request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '503':
          description: API key requests are temporarily unavailable.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error: Service unavailable
                message: >-
                  The application desk is temporarily closed. Please try again
                  later.
components:
  schemas:
    RequestApiKeyResponse:
      type: object
      properties:
        status:
          type: string
          enum:
            - received
        message:
          type: string
      required:
        - status
        - message
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
      required:
        - error
        - message
      example:
        error: Bad request
        message: Invalid request body

````