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.
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
Check Invoice / Retrieve Output
Developer Endpoints
GET /api/v1/request?service=<service>&tier=<tier>&txid=<txid> GET /api/v1/status?invoice_id=<invoice_id> GET /api/v1/artifact?invoice_id=<invoice_id> GET /api/v1/proof?invoice_id=<invoice_id> GET /api/v1/verify?invoice_id=<invoice_id>