Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Satellogic Aleph API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsatellogic.com%2Fsatellogic" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsatellogic.com%2Fsatellogic" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Satellogic Aleph API.
Create a new satellite imagery order
List all orders
Get order details
Update an order
Monitor Satellogic Aleph API operational status and events
GET STARTED
Patterns agents use Satellogic Aleph API for, with concrete tasks.
★ CRM Operations
Use the Satellogic Aleph API to perform crm operations programmatically. The API provides 19 endpoints covering core functionality including create a new satellite imagery order, list all orders, get order details.
Call POST /v2/orders to create a new satellite imagery order
Automated Analysis Management
Automate analysis operations by combining multiple Satellogic Aleph API endpoints. Agents can list all orders and then get order details in a single workflow.
Call GET /v2/orders to list all orders, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Satellogic Aleph API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.
Search Jentic for 'create a new satellite imagery order', load the operation schema, and execute with Jentic-managed credentials
19 endpoints — satellogic's aleph api v2 provides comprehensive access to satellite imagery and geospatial intelligence capabilities.
METHOD
PATH
DESCRIPTION
/v2/orders
Create a new satellite imagery order
/v2/orders
List all orders
/v2/orders/{order_id}
Get order details
/v2/orders/{order_id}
Update an order
/v2/orders/{order_id}/captures
List captures for an order
/v2/captures
List all captures
/v2/deliverables
List all deliverables
/v2/deliverables/{deliverable_id}
Get deliverable details
/v2/orders
Create a new satellite imagery order
/v2/orders
List all orders
/v2/orders/{order_id}
Get order details
/v2/orders/{order_id}
Update an order
/v2/orders/{order_id}/captures
List captures for an order
/v2/captures
List all captures
/v2/deliverables
List all deliverables
/v2/deliverables/{deliverable_id}
Get deliverable details
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Satellogic Aleph API by hand means running its OAuth2 client-credentials flow for a token, passing the contract id header, and tracking orders, captures, and deliverables yourself. Through Jentic you install once, import the Satellogic Aleph API from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Satellogic puts the order id in the URL path (/v2/orders/{order_id}), so a rule can pin your agent to one order. You choose the operations it may call, so an update like patching an order is not included unless you add it alongside the read operations.
Credential isolation
Your Satellogic Aleph API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a satellite imagery order' or 'list deliverables for a capture', and Jentic returns the matching Satellogic Aleph API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Satellogic Aleph API through Jentic.
What authentication does the Satellogic Aleph API use?
The Satellogic Aleph API uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a new satellite imagery order with the Satellogic Aleph API?
Yes. Use the POST /v2/orders endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Satellogic Aleph API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new satellite imagery order through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new satellite imagery order'. Jentic returns the matching Satellogic Aleph API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Satellogic Aleph API have?
The Satellogic Aleph API exposes 19 endpoints covering analysis, archive, captures operations.
Can I limit what my agent is allowed to do with the Satellogic Aleph API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Satellogic Aleph API operations and credentials the agent may use. Because the order id sits in the URL path (/v2/orders/{order_id}), you can pin the agent to a single order and grant only read operations such as GET /v2/orders/{order_id}, its captures, and deliverables. Patching an order via PATCH /v2/orders/{order_id} is not available to the agent unless you explicitly add it to the allowed set.
For Agents
Programmatically create a new satellite imagery order, list all orders. Covers 19 operations with apiKey, oauth2 authentication.
Use for: I need to a new satellite imagery order, I want to all orders, Search for order details, Find all an order
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Satellogic's Aleph API v2 provides comprehensive access to satellite imagery and geospatial intelligence capabilities. It supports ordering satellite imagery, searching archives via STAC-compliant endpoints, analyzing capture feasibility, tracking deliverables, and managing projects and user profiles. The API exposes 19 endpoints secured with apiKey, oauth2 authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>