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

# GET /v1/billing/rates

> Return the public pricing catalog, starter grant metadata, plan metadata, and meter-family launch rates

Return the public pricing catalog, starter grant metadata, plan metadata, and meter-family launch rates

<Info>
  Audience: application and coding agent.
</Info>

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/billing/rates"
  ```
</RequestExample>

<Info>
  `starterGrant` is included even though it is not a paid checkout plan. Agents should read it together with `GET /v1/billing` and `GET /v1/limits` to explain the included-call grant, overflow behavior, meter rates, and current account state without inferring from marketing copy.
</Info>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "pricing_catalog",
    "requestId": "req_2ZK8Q1W9F4M6P7R3",
    "version": "2026-06-18",
    "starterGrant": {
      "object": "starter_grant",
      "planKey": "sandbox_grant",
      "billingState": "sandbox_grant",
      "calls": 150,
      "renewable": false,
      "period": null,
      "overflowPlanKey": "payg",
      "note": "New organizations start on the starter grant; usage beyond the grant falls through to Pay As You Go rates once billing is activated."
    },
    "plans": [
      {
        "key": "payg",
        "displayName": "Pay As You Go",
        "kind": "metered",
        "meterFamilyPrices": [
          {
            "key": "standard_reads",
            "unitAmountUsd": 0.02
          }
        ]
      }
    ]
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/billing/rates to return the public pricing catalog, starter grant metadata, plan metadata, and meter-family launch rates. Preserve `requestId`, `traceparent` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff