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

# Estimate tier and credit cost



## OpenAPI

````yaml /openapi.public.json post /api/v3/estimates
openapi: 3.1.0
info:
  title: AstroM8 Public API
  version: 1.1.0
  description: >-
    Astrology calculations, reports, customer delivery, and enterprise
    workflows. Each operation declares whether it uses an API key or a customer
    session bearer token.
servers:
  - url: https://api.astrom8.com
    description: Production
security: []
tags:
  - name: Western
    description: Natal, relationship, return, progression, and transit calculations.
  - name: Vedic
    description: Lahiri sidereal Vedic calculations, matching, timing, and remedies.
  - name: Thai Astrology
    description: Thai calendar, auspicious timing, lunar, festival, and wheel tools.
  - name: Chinese & Korean
    description: BaZi, Qi Men Dun Jia, and Saju calculations.
  - name: Horoscopes
    description: Published daily and range horoscope content.
  - name: Reports
    description: Branded report generation and asynchronous job polling.
  - name: Tarot & Numerology
    description: Tarot spreads and Pythagorean numerology.
  - name: Uranian
    description: Uranian charts, midpoints, and planetary pictures.
  - name: Developer workflow
    description: Preflight capability eligibility and credit estimates.
  - name: Customer reports
    description: Session-authenticated report jobs and reusable brand profiles.
  - name: Customer delivery
    description: Session-authenticated webhooks and scheduled horoscope delivery.
  - name: Cultural Intelligence
    description: >-
      Enterprise API-key workflows for encrypted profiles, teams, and campaign
      content.
paths:
  /api/v3/estimates:
    post:
      tags:
        - Developer workflow
      summary: Estimate tier and credit cost
      operationId: estimateCapability
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                capability:
                  type: string
                  description: >-
                    Capability id from the published capability registry, for
                    example `western.synastry` or `western.natal-premium-pdf`.
              required:
                - capability
      responses:
        '200':
          description: >-
            Preflight result. `debit_on_submit` means the actual endpoint will
            debit on accepted submission.
          content:
            application/json:
              schema:
                type: object
                properties:
                  capability:
                    type: string
                  endpoint:
                    type: string
                  execution:
                    type: string
                    enum:
                      - sync
                      - async
                  credits:
                    type: integer
                  required_tier:
                    type: string
                    enum:
                      - free
                      - starter
                      - pro
                  tier_allowed:
                    type: boolean
                  sufficient_credits:
                    type: boolean
                  unlimited_credits:
                    type: boolean
                  debit_on_submit:
                    type: boolean
                    const: true
                required:
                  - capability
                  - endpoint
                  - execution
                  - credits
                  - tier_allowed
                  - sufficient_credits
                  - debit_on_submit
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          description: The API key tier cannot use this operation.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JsonError'
      security:
        - ApiKeyAuth: []
components:
  responses:
    Unauthorized:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/JsonError'
          example:
            error: unauthorized
            message: Invalid API key
            code: '401'
            request_id: 01HQXYZ...
  schemas:
    JsonError:
      type: object
      required:
        - error
        - message
      properties:
        error:
          type: string
          description: >-
            Stable slug (e.g. unauthorized, payment_required,
            internal_server_error).
        message:
          type: string
          description: Human-readable message safe for clients.
        code:
          type: string
          description: Optional provider-specific code.
        request_id:
          type: string
          description: Correlation id when middleware sets it.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: Use the raw API key as the Bearer token, or send X-API-Key instead.

````