Infrastructure API

Purpose

The Gravity API provides machine-readable access to the same invoice-bound workflow used by Gravity services.

Software systems can create service requests, receive invoice/payment instructions, monitor confirmation status, retrieve finalized records, and verify issued outputs.

API requests follow the same deterministic Gravity pipeline used by the public service pages:

request → invoice → confirmations → execution → package → retrieval → verification

Human users typically begin from the Relay, Case, or Certification service pages. Software systems may interact with the same workflow programmatically through the API.

What This API Is For

The GravityBTC API provides structured access to service requests, invoice-bound status checks, artifact retrieval, verification records, and verification workflows.

It exists so clients can follow a deterministic process: select a service, create or reference an invoice, wait for required confirmations, execute the service, retrieve issued records, and verify outputs.

These endpoints are public interface references. They do not grant administrative access, repository access, wallet access, or control over GravityBTC infrastructure.

Machine Discovery

Automation clients should begin with the service registry before creating a request. The registry describes available Gravity services, supported tiers, and workflow identifiers so software systems can select Relay, Case, or Certification without relying on hard-coded assumptions.

Gravity is designed so software agents can discover capabilities rather than rely on undocumented behavior. Machine clients may inspect service availability, authority boundaries, and operational state before interacting with invoice-bound workflows.

Service selection is registry-driven: Relay is used for transaction observation and operational records, Case is used for structured review of a Bitcoin transaction or reference, and Certification is used when a durable verification package is required.

Authority metadata describes which Gravity authority owns the workflow, what boundaries apply, what state should exist after interaction, and what proof or retrieval path is expected.

GET /api/v1/services.json
Machine-readable service registry (JSON)

GET /api/v1/authority-registry.json
Machine-readable authority registry (pending review)

For a human-readable example of the type of structured record a client may receive, see Sample Records.

Bitcoin-paid access to Gravity services without exposing wallets, RPC, shell access, private ledgers, anchors, or operator controls.

What the API maintains

GravityBTC Infrastructure API maintains the client workflow for supported paid services:

Request → Invoice → QR Payment → Confirmations → Processing → Record → Proof → Retrieval.

Certification Case Relay

Create Invoice

Service

Tier

Record Title Group Label Record Context Certification Reference Bitcoin TXID / Reference

Check Invoice / Retrieve Output

Invoice ID

Developer Endpoints

Relay
GET /bridge?service=GRV-RELAY&tier=T1&txids=<txid>&record_title=<title>&group_label=<group>&record_context=<context>

Case
GET /bridge?service=GRV-CASE&tier=FORENSIC&txid=<txid>&record_title=<title>&group_label=<group>&record_context=<context>

Certification
GET /bridge?service=GRV-CERT&tier=T1&cert_reference=<reference>&record_title=<title>&group_label=<group>&record_context=<context>

Status
GET /api/v1/status?invoice_id=<invoice_id>

Verification
GET /api/v1/verify?invoice_id=<invoice_id>

What happens next: Gravity confirms settlement, finalizes the package, activates retrieval, and keeps verification available so the client or connected system can return later with confidence.