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

# Accept the Agent Simulation Terms for the current organization

> Records the acceptance, by an owner or admin of the organization, of the current Agent Simulation Terms outside a plan start: an organization on a plan accepting a new version on its next visit. The exact text and its hash, the consent wording shown, and the address, browser and country the click came from are kept. version and sha256 are the ones the page showed; an older version answers 409 terms_stale. Accepting the current version again returns the acceptance on record. Other members get 403 forbidden; staff working in the organization through the switcher get 403 membership_required and nothing is recorded.



## OpenAPI

````yaml https://api.zeroclick.io/openapi.json post /v1/organizations/current/agent-simulation-terms/accept
openapi: 3.0.0
info:
  title: ZeroClick API
  description: >-
    REST API for managing ZeroClick sellers, services, pricing, usage, and
    analytics. Authenticate with an API key from the ZeroClick dashboard.
  version: 1.0.0
servers:
  - url: https://api.zeroclick.io
security:
  - bearerAuth: []
tags:
  - name: API keys
  - name: Sellers
  - name: Services
  - name: Meters
  - name: Plans
  - name: Plan meter prices
  - name: Usage
  - name: Analytics
  - name: Agentify
  - name: Stripe Connect
  - name: Sandbox
  - name: Organizations
  - name: Users
paths:
  /v1/organizations/current/agent-simulation-terms/accept:
    post:
      tags:
        - Organizations
      summary: Accept the Agent Simulation Terms for the current organization
      description: >-
        Records the acceptance, by an owner or admin of the organization, of the
        current Agent Simulation Terms outside a plan start: an organization on
        a plan accepting a new version on its next visit. The exact text and its
        hash, the consent wording shown, and the address, browser and country
        the click came from are kept. version and sha256 are the ones the page
        showed; an older version answers 409 terms_stale. Accepting the current
        version again returns the acceptance on record. Other members get 403
        forbidden; staff working in the organization through the switcher get
        403 membership_required and nothing is recorded.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                version:
                  type: string
                  minLength: 1
                  maxLength: 80
                sha256:
                  type: string
                  pattern: ^[0-9a-f]{64}$
                consentText:
                  type: string
                  minLength: 1
                  maxLength: 1000
                clientIp:
                  anyOf:
                    - type: string
                      format: ipv4
                      pattern: >-
                        ^(?:(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])$
                    - type: string
                      format: ipv6
                      pattern: >-
                        ^(([0-9a-fA-F]{1,4}:){7}[0-9a-fA-F]{1,4}|([0-9a-fA-F]{1,4}:){1,7}:|([0-9a-fA-F]{1,4}:){1,6}:[0-9a-fA-F]{1,4}|([0-9a-fA-F]{1,4}:){1,5}(:[0-9a-fA-F]{1,4}){1,2}|([0-9a-fA-F]{1,4}:){1,4}(:[0-9a-fA-F]{1,4}){1,3}|([0-9a-fA-F]{1,4}:){1,3}(:[0-9a-fA-F]{1,4}){1,4}|([0-9a-fA-F]{1,4}:){1,2}(:[0-9a-fA-F]{1,4}){1,5}|[0-9a-fA-F]{1,4}:((:[0-9a-fA-F]{1,4}){1,6})|:((:[0-9a-fA-F]{1,4}){1,7}|:))$
                clientUserAgent:
                  type: string
                  minLength: 1
                  maxLength: 512
                clientCountry:
                  type: string
                  minLength: 2
                  maxLength: 2
              required:
                - version
                - sha256
                - consentText
      responses:
        '200':
          description: Default Response
          content:
            application/json:
              schema:
                type: object
                properties:
                  accepted:
                    type: boolean
                    enum:
                      - true
                  version:
                    type: string
                  acceptedAt:
                    type: string
                required:
                  - accepted
                  - version
                  - acceptedAt
                additionalProperties: false
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key created in the ZeroClick dashboard under Settings → API keys.
        Keys start with `zc_`. Send them as `Authorization: Bearer zc_...`.

````

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