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

# Usage history

> **Requires `x-api-key` header.**

Rate limit: 5 requests/second per API key.

Returns the last 500 requests for this key, newest first. Includes both `/research` calls and Direct API calls (`/company-tech-stack`, `/company-linkedin`, `/company-linkedin-posts`, `/company-contact`, `/company-jobs`, `/page-scrape`, `/page-analyze`, `/page-find`, `/company-search`, `/company-search-count`, `/person-search`, `/person-search-count`, `/person-email`, `/person-linkedin-url`, `/person-linkedin`, `/linkedin-post`, `/linkedin-post-reactions`, `/linkedin-post-comments`, `/company-linkedin-url`). Use limit and offset for pagination.

**Research entries** have `model` set to the synthesis model used (e.g. `gemini-2.5-flash`) and `prompt` is the research question.

**Direct API entries** have `model: "none"` and `prompt` is formatted as `endpoint:input` (e.g. `company-contact:stripe.com`, `company-jobs:stripe.com`, `company-linkedin-posts:https://linkedin.com/company/stripe`, `page-find:stripe.com`, `person-email:Patrick Collison:stripe.com`, `person-linkedin-url:Patrick Collison:stripe.com`, `company-linkedin-url:stripe.com`, `person-linkedin:https://linkedin.com/in/username`, `linkedin-post:https://linkedin.com/feed/update/urn:li:activity:123`, `linkedin-post-reactions:https://linkedin.com/feed/update/urn:li:activity:123`, `linkedin-post-comments:https://linkedin.com/feed/update/urn:li:activity:123`). The `result` field contains the raw structured data from the endpoint.



## OpenAPI

````yaml /openapi.json get /usage
openapi: 3.0.3
info:
  title: Huntr — The GTM Intelligence API
  description: >-
    Give AI agents company, people, contact, and web intelligence through one
    API. Search accounts, build targeted lists, enrich leads, find contacts, and
    uncover buying signals.


    **Authentication:** Authenticated endpoints require an `x-api-key` header
    with your Huntr API key. Get a key by signing up via `POST /keys/create`.
    Public endpoints (pricing, sign-up, health) work without a key.


    **Rate limit:** 5 requests/second per API key on authenticated endpoints.
  version: 2.0.0
servers:
  - url: https://api.tryhuntr.com
security: []
tags:
  - name: Research
    description: >-
      Research one company, person, team, or focused business question and
      return a sales-ready answer. Lite, standard, and deep tiers.
  - name: Companies
    description: >-
      Search companies and enrich firmographics. Per-result pricing on search;
      count endpoints are free.
  - name: People
    description: >-
      Search people and enrich contacts — work email, phone, and related lookup
      endpoints.
  - name: LinkedIn
    description: >-
      LinkedIn URL discovery, company and profile pages, posts, reactions, and
      comments.
  - name: X
    description: X profiles, posts, search results, and thread context.
  - name: Web
    description: >-
      Find and analyze pages on a domain, plus tech stack, domain contacts, and
      job postings.
  - name: Account
    description: >-
      Sign up, verify email, recover keys, check balance, view usage, add
      credits, and read the public pricing matrix.
  - name: System
    description: Health check.
paths:
  /usage:
    get:
      tags:
        - Account
      summary: Usage history
      description: >-
        **Requires `x-api-key` header.**


        Rate limit: 5 requests/second per API key.


        Returns the last 500 requests for this key, newest first. Includes both
        `/research` calls and Direct API calls (`/company-tech-stack`,
        `/company-linkedin`, `/company-linkedin-posts`, `/company-contact`,
        `/company-jobs`, `/page-scrape`, `/page-analyze`, `/page-find`,
        `/company-search`, `/company-search-count`, `/person-search`,
        `/person-search-count`, `/person-email`, `/person-linkedin-url`,
        `/person-linkedin`, `/linkedin-post`, `/linkedin-post-reactions`,
        `/linkedin-post-comments`, `/company-linkedin-url`). Use limit and
        offset for pagination.


        **Research entries** have `model` set to the synthesis model used (e.g.
        `gemini-2.5-flash`) and `prompt` is the research question.


        **Direct API entries** have `model: "none"` and `prompt` is formatted as
        `endpoint:input` (e.g. `company-contact:stripe.com`,
        `company-jobs:stripe.com`,
        `company-linkedin-posts:https://linkedin.com/company/stripe`,
        `page-find:stripe.com`, `person-email:Patrick Collison:stripe.com`,
        `person-linkedin-url:Patrick Collison:stripe.com`,
        `company-linkedin-url:stripe.com`,
        `person-linkedin:https://linkedin.com/in/username`,
        `linkedin-post:https://linkedin.com/feed/update/urn:li:activity:123`,
        `linkedin-post-reactions:https://linkedin.com/feed/update/urn:li:activity:123`,
        `linkedin-post-comments:https://linkedin.com/feed/update/urn:li:activity:123`).
        The `result` field contains the raw structured data from the endpoint.
      parameters:
        - name: limit
          in: query
          schema:
            type: integer
            default: 10
            maximum: 500
          description: Number of entries to return.
        - name: offset
          in: query
          schema:
            type: integer
            default: 0
          description: Entries to skip (for pagination).
      responses:
        '200':
          description: Usage history, newest first.
          content:
            application/json:
              schema:
                type: object
                properties:
                  requests:
                    type: array
                    description: Paginated slice of the last 500 requests, newest first.
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                          description: >-
                            Unique request ID (same as request_id in the
                            research response).
                        prompt:
                          type: string
                          description: The research prompt that was submitted.
                        result:
                          description: >-
                            The research result that was returned. String for
                            free-text, object for schema responses.
                        tier:
                          type: string
                          enum:
                            - lite
                            - standard
                            - deep
                          description: Tier the request ran at.
                        model:
                          type: string
                          description: Synthesis model used.
                        cost:
                          type: number
                          description: Amount charged in USD for this request.
                        capabilities_used:
                          type: array
                          items:
                            type: string
                          description: Capabilities the agent ran for this request.
                        timestamp:
                          type: string
                          format: date-time
                          description: ISO 8601 timestamp of when the request completed.
                  total_requests:
                    type: integer
                    description: >-
                      Total number of requests stored for this key (up to 500
                      most recent).
                  total_cost:
                    type: number
                    description: Sum of cost across all stored requests in USD.
              examples:
                research:
                  summary: Research request entry
                  value:
                    requests:
                      - id: req_1746123456_ab3x9k
                        prompt: Find CEO of Stripe
                        result: Patrick Collison is the CEO of Stripe...
                        tier: standard
                        model: gemini-2.5-flash
                        cost: 0.027
                        capabilities_used:
                          - search_and_scrape
                          - news_search
                        timestamp: '2026-05-03T12:00:45Z'
                    total_requests: 42
                    total_cost: 1.28
                directApi:
                  summary: Direct API entries
                  value:
                    requests:
                      - id: req_1746123456_jp1x2y
                        prompt: company-jobs:stripe.com
                        result:
                          jobs:
                            - title: Software Engineer
                              location: Remote
                              url: https://stripe.com/jobs/1
                          total: 1
                          is_hiring: true
                          source: greenhouse
                        tier: lite
                        model: none
                        cost: 0.012
                        capabilities_used:
                          - job_postings_scrape
                        timestamp: '2026-05-03T12:02:10Z'
                      - id: req_1746123456_fp1x2y
                        prompt: page-find:stripe.com
                        result:
                          pages:
                            - url: https://stripe.com/pricing
                              score: 0.95
                              matched_keywords:
                                - pricing
                              match_reasons:
                                - exact_path_segment
                          total_sitemap_urls: 500
                          matched: 1
                        tier: lite
                        model: none
                        cost: 0.005
                        capabilities_used: []
                        timestamp: '2026-05-03T12:03:10Z'
                    total_requests: 42
                    total_cost: 1.28
        '401':
          description: Invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message.
      required:
        - error
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Your Huntr API key. Get one at tryhuntr.com. Pass as x-api-key header on
        all authenticated requests.

````