Build against validated Litecoin data.

Getting Started

Quickstart

Create an API key in your account, then pass it as a bearer token. Use `fx_test_` keys while evaluating integrations and `fx_live_` keys for production traffic on paid Xtract plans.

curl -H "Authorization: Bearer fx_test_************" \
  https://forcex.com/xtract/v1/litecoin/chain/home

Base URL

The current production API is path-based on `forcex.com`.

https://forcex.com/xtract/v1/litecoin

Endpoint tables below use short paths such as `/chain/home`. Prepend the base URL when making requests.

Authentication

Every Xtract operation requires a bearer API key with the `xtract` scope.

Authorization: Bearer fx_live_************

Response Format

Successful responses use a strict `data` plus `meta` envelope. Optional expansion payloads appear in `included` when an endpoint supports `?include=`.

{
  "data": {
    "chain": "litecoin",
    "tip_height": 3118767,
    "tip_time": "2026-06-03T17:22:51Z"
  },
  "meta": {
    "request_id": "req_...",
    "served_at": "2026-06-03T17:23:02Z",
    "served_from": "indexed_store",
    "validation": {
      "scope": "chain",
      "status": "validated",
      "validated_height": 3118767,
      "validated_at": "2026-06-03T17:22:58Z",
      "lag_blocks": 0
    },
    "dataset_version": "v2.6",
    "credit_cost": 1,
    "included_expansions": []
  }
}

Validation Metadata

Validation is first-class in Xtract. Chain endpoints report the validated chain height used to serve the response. Control-plane endpoints report validation as not applicable instead of over-certifying data they do not read.

For the current scalar validation surface, use `GET /chain/validation`.

Credits & Rate Limits

Requests consume credits. Simple point lookups usually cost 1 credit; richer `?include=` expansions and batch requests cost more. Responses include `meta.credit_cost` and rate-limit headers where applicable.

Sandbox keys are always Free-effective: 30,000 period credits, 30 credits/minute, and 5 credits/second.

RateLimit-Limit: 20;w=1, 200;w=60, 300000;w=2592000
RateLimit-Remaining: 183
RateLimit-Reset: 42
RateLimit-Cost: 1

Retry-After: 17
X-Request-Id: req_...

Pagination

Paginated chain listings use opaque cursors. Page 1 anchors the walk to a validated chain height, and later pages keep that anchor so a long listing remains consistent while new blocks arrive.

Chart Ranges

Chart endpoints use `start` and `end` query parameters with half-open range semantics: `[start, end)`. Weekly buckets are anchored to Monday 00:00 UTC.

GET /charts/network?metrics=tx_count,avg_fee_atomic_units&start=2026-05-01&end=2026-06-01&grain=day

The older `from` and `to` aliases are accepted for compatibility during the transition, but new integrations should use `start` and `end`.

Errors

Error responses keep the same `meta` block for request tracing.

{
  "error": {
    "code": "auth_required",
    "message": "Authentication required."
  },
  "meta": {
    "request_id": "req_...",
    "served_at": "2026-06-03T17:23:02Z",
    "served_from": "control_plane",
    "validation": {
      "scope": "account",
      "status": "not_applicable",
      "validated_height": null,
      "validated_at": null,
      "lag_blocks": null
    }
  }
}

Endpoint Reference

This catalog mirrors the current OpenAPI 0.2.0 operation set. Use the per-endpoint pages for request examples and integration notes, and the OpenAPI document for exhaustive schemas and generated-client inputs.

Chain

Mempool

Charts

Developer

OpenAPI

The generated OpenAPI 3.1 contract is the source for schemas, operation ids, headers, and generated clients.