Arlula
Arlula is a satellite imagery marketplace and API platform providing programmatic access to archive and tasking satellite imagery from multiple providers. The Arlula API enables developers to search the global satellite archive, discover tasking opportunities, place imagery orders, and download delivered datasets including GeoTIFF imagery, preview images, and metadata files.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Arlula the way a machine reads it — 81 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Arlula scores 61.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Arlula
Each block below is one kind of artifact we hold for Arlula. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Arlula Archive API
Search and order historical satellite imagery
Arlula Connection API
API connection testing
Arlula Orders API
Manage orders, campaigns, datasets, and resources
Arlula Tasking API
Schedule future satellite captures
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Arlula Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Arlula Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Arlula Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Archive Search
Search a global satellite image archive from multiple providers using area-of-interest (polygon/bounding box) and temporal filters to find available historical scenes.
Satellite Tasking
Commission future satellite captures by searching tasking opportunities and placing orders for specific areas of interest and time windows.
Multi-Provider Access
Access imagery from multiple satellite providers through a single unified API, enabling price and resolution comparisons across providers.
Bundle Selection
Choose from available product bundles (e.g., analytic, visual) when ordering scenes to match data requirements and budget.
Dataset Download
Download delivered imagery resources including GeoTIFF files, preview images, and metadata through the Orders API after capture and processing.
Batch Ordering
Place multiple archive or tasking orders in a single batch API request to efficiently process large-scale imagery acquisitions.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Arlula Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Arlula API Rules
SPECTRALArlula API Rules
SPECTRALJSON Schema 19
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ArchiveOrderRequest
JSON SCHEMAArchiveScene
JSON SCHEMAArchiveSearchRequest
JSON SCHEMABatchArchiveOrderRequest
JSON SCHEMABatchTaskingOrderRequest
JSON SCHEMABundle
JSON SCHEMACampaign
JSON SCHEMACampaignsListResponse
JSON SCHEMACancelResponse
JSON SCHEMADataset
JSON SCHEMADatasetsListResponse
JSON SCHEMAOrderResponse
JSON SCHEMAOrder
JSON SCHEMAOrdersListResponse
JSON SCHEMAResource
JSON SCHEMATaskingOpportunity
JSON SCHEMATaskingOrderRequest
JSON SCHEMATaskingSearchRequest
JSON SCHEMATestResponse
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Arlula Archive Order Request Structure
JSON STRUCTUREArlula Archive Scene Structure
JSON STRUCTUREArlula Archive Search Request Structure
JSON STRUCTUREArlula Batch Archive Order Request Structure
JSON STRUCTUREArlula Batch Tasking Order Request Structure
JSON STRUCTUREArlula Bundle Structure
JSON STRUCTUREArlula Campaign Structure
JSON STRUCTUREArlula Campaigns List Response Structure
JSON STRUCTUREArlula Cancel Response Structure
JSON STRUCTUREArlula Dataset Structure
JSON STRUCTUREArlula Datasets List Response Structure
JSON STRUCTUREArlula Order Response Structure
JSON STRUCTUREArlula Order Structure
JSON STRUCTUREArlula Orders List Response Structure
JSON STRUCTUREArlula Resource Structure
JSON STRUCTUREArlula Tasking Opportunity Structure
JSON STRUCTUREArlula Tasking Order Request Structure
JSON STRUCTUREArlula Tasking Search Request Structure
JSON STRUCTUREArlula Test Response Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Arlula Archive Scene Example
EXAMPLEArlula Bundle Example
EXAMPLEArlula Campaign Example
EXAMPLEArlula Dataset Example
EXAMPLEArlula Order Example
EXAMPLEArlula Resource Example
EXAMPLEArlula Test Response Example
EXAMPLEScroll within the panel for all 19 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Agricultural Monitoring
Search and order archive or tasking imagery to monitor crop health, irrigation patterns, and field conditions over growing seasons.
Environmental Change Detection
Acquire multi-temporal satellite imagery to detect deforestation, coastal erosion, urban expansion, or disaster impact areas.
Infrastructure Inspection
Order high-resolution imagery for remote inspection of pipelines, power lines, roads, and construction site progress monitoring.
Disaster Response
Rapidly search and order post-event imagery to assess damage extent and support emergency response and recovery planning.
Resources
Every other property we hold for Arlula — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/arlula · machine-readable index on apis.io