Data Sphere handbook

Practical guide to using Data Sphere, a platform for finding, licensing and buying satellite imagery from named providers, with assurance of who may use the data and for what: running searches, ordering imagery, and integrating via the API. For endpoint-level reference jump to the API docs. The full public documentation, including the API guides, is at https://docs.datasphere.astrodynamic.space.

01 — Quick start

Find imagery in five steps

The fastest way to evaluate Data Sphere is to run a search and inspect a result.

01

Open the search page

Navigate to /search.

02

Draw an AOI

Use Draw area or the toolbar rectangle to bound the region.

03

Apply filters

Date window, cloud cover, GSD, sensor, provider.

04

Inspect a result

Drill into a card to view metadata, footprint, and assets.

05

Add to basket

Check out via Stripe; download links arrive by email.

Heads up. You can browse the catalogue without an account, but ordering and downloads require sign-in. Create one at /register.

02 — Accounts & roles

Who can do what

Data Sphere uses an organisation model: every user belongs to one or more orgs, and each org has a role-based access control list.

Roles

  • Owner — full administrative access; manages billing, members, and provider configuration.
  • Admin — everything an owner can do except removing the owner or deleting the organisation.
  • Member — can search, order, and download under the org's billing relationship.
  • Provider — a separate org type that publishes catalogues onto the platform.

Invitations

Owners can invite new members from the dashboard. Invitations are single-use, time-limited tokens signed against your org slug.

04 — Datasets & products

Collections, items, packages

  • Collection — the provider's grouping (e.g. Sentinel-2 L2A).
  • Item — one capture: a single timestamp, footprint, and asset bundle.
  • Aggregate — a search-results convenience: items rolled up by collection × bbox.
  • Package — a curated subscription bundle (used by the streaming feed).

STAC compliance

All catalogue records conform to STAC 1.0. Where providers ship custom extensions we surface them under the filters key on the item.

05 — Basket & checkout

Order an item

Add results to your basket from any item or aggregate page. Checkout opens a Stripe Checkout session keyed to your organisation; we never store card details.

Pricing

Pricing is per-item and is set by the originating provider. Free tiers are clearly labelled.

Provider payouts

Stripe Connect routes funds directly to the provider's connected account on order completion. Each provider is paid the cost it quotes for each order line. Data Sphere's margin is added on top of that cost in the price the buyer pays.

06 — Downloads

How orders are delivered

Once an order is paid, its order page lists every purchased file with a download link behind sign-in. Reach it from your dashboard, which lists your orders; each download is checked against your account's entitlement before it is served.

Bulk downloads

For large baskets, the platform stages an asset zip server-side. The link points to the same download endpoint with a manifest token.

07 — Subscriptions

Data packages

A curated, subscription-style bundle of items is called a package. Its contents are retrieved through paginated or streaming HTTP endpoints on the public API rather than a push channel; there is no WebSocket or Server-Sent Events feed on the platform.

See the API docs for endpoint details.

08 — Providers

Publishing a catalogue

Providers join by invitation from Data Sphere staff and set up their organisation from it. Once that is done, the dashboard exposes:

  • Bulk catalogue upload (STAC items + collections)
  • Pricing controls per collection
  • Stripe Connect onboarding for payouts

09 — Saved searches

Persisting and sharing a query

Any search can be saved with a one-click action on the results page. Saved searches:

  • Generate a sharable URL that re-runs the query when opened.
  • Are scoped to your account and not visible to other users in your org unless explicitly shared.

10 — Integrations

Programmatic access

The REST API lets you list, stream and download the data your account has bought. Auth is via an API token issued from the dashboard, sent as Authorization: Token <key>. A browser session cookie is not accepted.

Detailed endpoint reference: /api-docs.

Common patterns

Your items, paginatedGET /api/items/ Signed download URLsGET /api/grants/ Single item lookupGET /api/item/v1/<id>/

There is no package name to supply. What you can read is decided by the delivery grants your orders created, so an unfiltered call to /api/items/ returns everything you own, and collection, from, to, assets and order narrow it from there.

11 — Guided walkthrough

New here? Follow the journey

The sections above are the reference; these five pages are the same ground walked step by step, from a bare search page to a fulfilled order.

12 — Buyer FAQ

Buying on Data Sphere

Does my licence cover the imagery I want to buy?
Your licence (Standard, Educational, Commercial or Military) decides which gated imagery you can buy, by resolution and by how recent the capture is. Adding an item to your basket checks it; if your licence does not cover the item you will see a notice with a link to the licence explanation and a path to upgrade.
Where do I find my downloads after purchase?
Once an order is fulfilled, its order page in your dashboard lists a Download action per asset. Links are signed and time-limited; you can re-fetch as many times as needed within the delivery grant's validity window.
How do refunds work?
Refund requests go to operations via the dashboard support form; include the order id.

13 — Provider FAQ

Selling on Data Sphere

How do I onboard as a provider?
Register a provider organisation, then complete Stripe Connect Express onboarding from the provider dashboard. Stripe handles identity and bank-detail verification on our behalf; charges and payouts are enabled once Stripe confirms the account. We never store your banking details.
How does Data Sphere's margin work?
Each provider is paid the cost it quotes for each order line. Data Sphere's margin is added on top of that cost in the price the buyer pays. The cost settles to your Stripe Connect balance on Stripe's own payout schedule. VAT obligations remain with you as the provider.
How do I list collections and assets?
A listing wraps a STAC Collection plus a pricing model, ingested via the provider dashboard. Asset files can be platform-hosted (uploaded to our storage, we serve signed URLs) or provider-hosted (you provide a URL template and verify requests yourself).
When are provider payouts processed?
Payouts run on Stripe Connect Express's own schedule once a charge settles. Payout history and the next scheduled date appear in your Stripe Express dashboard, reachable from the provider dashboard.
What licensing rules apply?
You must hold the right to redistribute any data you list. Define per-collection licensing constraints, export-control flags, geographic exclusions and a required licence; the licensing engine evaluates these against every buyer at basket time.

14 — API FAQ

Programmatic access, in brief

How do I authenticate API requests?
Generate a named token from your dashboard's API settings and send it as an Authorization: Token header. A browser session cookie is not accepted on this API. Tokens are long-lived by default; revoke one individually if it is compromised.
What are the rate limits?
Each plan tier carries its own per-minute request ceiling; a plan with no API access on it is refused entirely. Contact operations if you need a higher limit than your current plan allows.
Where is the endpoint reference?
See API docs and §10 above for the item, stream, grant and package endpoints, request shapes, and what each field returns.

15 — Help & support

Get in touch

Stuck? The team monitors info@astrodynamic.space during UK business hours. For commercial enquiries see /commercial.

Terms: /terms.