The ground picture, as an interface.
Query coverage, public listings, standards metadata, and draft BPI messages through a read-only, API-key-authenticated surface built on the same models as BeamDesk and BeamGround.
A deliberately narrow, read-only partner surface.
The current machine API answers discovery and interoperability questions. Marketplace writes remain in authenticated BeamGround workflows rather than being implied by the public API.
| Resource | Method and path | What it returns |
|---|---|---|
| Coverage | GET /api/public/v1/coverage?lat=&lon= | Point coverage, registered fleet context, sky metrics, and computation provenance. |
| Opportunities | GET /api/public/v1/bpi/opportunities?lat=&lon= | A draft BPI delivery-opportunity message for the registered sweep, or an explicit no-window result. |
| Public listings | GET /api/public/v1/listings?bbox= | Discoverable listings inside a bounding box, with approximate centroids and no owner identity. |
| Standards registry | GET /api/public/v1/standards | Issuer, edition, source link, implementation depth, and caveat for each registry entry. |
Keys belong to organizations, not browser sessions.
Machine clients send an individually revocable API key as a Bearer token. BeamDesk stores only the key’s SHA-256 hash and meters requests per key; a person’s portal session is not reused for integrations.
Fleet-dependent routes return an unavailable response when no real registered fleet is installed. They do not silently substitute the mock network.
GET /api/public/v1/coverage?lat=32.1&lon=34.8 HTTP/1.1
Host: api.beamdesk.space
Authorization: Bearer <api-key>
Accept: application/jsonThe epoch and method travel with the answer.
Coverage is meaningful only in the context of the fleet and sweep that produced it. The response therefore carries provenance alongside the modeled result.
{
"point": { "lat": 32.1, "lon": 34.8 },
"fleet": { "...": "registered fleet and epoch" },
"sky": { "...": "coverage metrics" },
"provenance": {
"sweep": "<registered sweep>",
"generatedAt": "<ISO-8601 timestamp>",
"method": "<computation method>",
"beamMaskDeg": "<registered mask>",
"note": "<source note>"
}
}Coverage, capacity, and implementation evidence.
Coverage
Evaluate a coordinate against the installed fleet and receive the orbital context needed to interpret the result.
Opportunities
Retrieve predicted delivery windows expressed as a draft BPI opportunity for the current registered sweep.
Public listings
Search a bounding box for listed ground while exact boundaries and owner identity stay inside the marketplace workflow.
Standards metadata
Inspect source bodies, revisions, implementation depth, and caveats as structured data rather than relying on a logo wall.
BPI capability
Retrieve the committed conformance record and broker-authored capability message shapes for parser and workflow development.
Explicit degradation
Callers receive ordinary HTTP errors and an explicit fleet-unavailable state instead of an answer assembled from mixed data modes.
Interoperability work, with its boundary attached.
The Beamed Power Interface gives capabilities, opportunities, and related records a machine-readable shape. Its present status must remain visible anywhere those messages are consumed.
BeamDesk-authored draft
BPI 0.2 has not been published by a standards body. BeamDesk is currently its sole implementation.
Broker capability, not attestation
BeamDesk’s claim is the broker role at L1. A capability it emits from its roster is a pre-filled broker draft, not an operator’s declaration.