generated: '2026-08-13'
method: searched
source:
- openapi/_original/revenuebase-openapi.json
- openapi/_original/revenuebase-contact-refresh-openapi.json
- https://docs.revenuebase.ai/api-reference/v2/authentication
- https://docs.revenuebase.ai/api-reference/v2/rate-limits
- live probes of api.revenuebase.ai
api: Revenuebase API v2
base_url: https://api.revenuebase.ai
authentication:
  style: api-key-header
  header: x-key
  ref: authentication/revenuebase-authentication.yml
idempotency:
  supported: false
  detail: >-
    No idempotency key mechanism is documented. Batch operations are made safe
    instead via server-issued process_id job tracking (submit -> poll -> download).
pagination:
  style: none
  detail: >-
    No cursor/offset pagination. Result-set size is controlled by request-body
    params: organization/resolve result_count (1-10), organization/discover
    result_count (1-10000) with min_similarity_score (0-0.95). Batch jobs are
    retrieved by process_id rather than paged.
versioning:
  style: uri-path
  current: v2
  ref: lifecycle/revenuebase-lifecycle.yml
rate_limiting:
  signaling: headers
  headers:
  - X-RateLimit-Limit
  - X-RateLimit-Remaining
  - X-RateLimit-Reset
  status: 429
  known_limits:
  - endpoint: POST /v2/email/verify
    limit: 5 requests/second
error_envelope:
  format: mixed
  detail: >-
    Two envelopes across two services. Revenuebase API v2 returns application/json
    with FastAPI HTTPValidationError for 422 and a string detail/error-code for
    400/401/402. The newer contact-refresh service returns RFC 9457
    application/problem+json with type/title/status/detail. Observed live.
  ref: errors/revenuebase-problem-types.yml
request_tracing:
  supported: partial
  field: request_id
  location: response body
  detail: >-
    The contact-refresh service returns a request_id (UUID) in both its success
    envelope (RefreshEmailResponse.request_id) and its problem+json error bodies.
    The v2 email/organization/jobs/account endpoints return no request id and no
    correlation header.
schema_versioning:
  supported: partial
  field: schema_version
  detail: >-
    RefreshEmailResponse carries an integer schema_version (default 2) alongside the
    URI-path API version — a payload-level version signal the older v2 responses do
    not have.
agent_surfaces:
  llms_txt: https://docs.revenuebase.ai/llms.txt
  mcp: https://docs.revenuebase.ai/mcp
  agent_card: https://docs.revenuebase.ai/.well-known/agent-card.json
  agent_skills: https://docs.revenuebase.ai/.well-known/agent-skills/index.json
  detail: >-
    All four agent surfaces live on the documentation host and are read-only over
    documentation content. None of them can invoke the data API; that requires a
    direct REST call with an x-key header. See mcp/revenuebase-tool-crosswalk.yml.
metering:
  model: credits
  detail: >-
    Usage is metered in credits. A Valid or Invalid email result deducts 1 credit;
    organization/resolve deducts 1 credit per request; organization/discover
    deducts credits only for results at/above min_similarity_score. Balance via
    GET /v2/account/balance; 402 when insufficient.
join_keys:
  detail: >-
    Data-model join convention: join on RBID, RBID_ORG, or LINKEDIN_URL — never on
    email address. All dataset emails are pre-verified valid.