Install Jentic One Beta

Connect the Off-Nadir Delta API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Off-Nadir Delta 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%2Foffnadir-delta.com%2Foffnadir-delta" | sh

Step 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%2Foffnadir-delta.com%2Foffnadir-delta" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Off-Nadir Delta API.

Query Delta Signals by bbox, start_date and end_date, categories, min_severity_band, and stages, paging with a cursor

Follow one event end to end with its thread, its recorded changes from /api/v1/developments, and its related events

Search Sentinel-1, Sentinel-2, and NISAR scene metadata over a bbox and plan imagery for an event by analysis_goal such as flood_mapping

Predict the next satellite passes over a lat and lon point and rank events by imaging-collection priority

GET STARTED

Start building with Off-Nadir Delta API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Off-Nadir Delta API for, with concrete tasks.

★ AI OSINT analyst agent

An analyst's agent answers 'what happened near this place this week and can we see it from orbit'. Through Jentic it searches for 'query geolocated world event signals', loads the Off-Nadir Delta querySignals operation, and calls it with a bbox and date window, then reads the event thread and plans imagery for the most severe event. The key is attached at call time, and metered calls spend the key owner's token balance, so the agent can call GET /api/v1/usage first to check it can afford the query.

Call GET /api/v1/signals with a bbox around the Strait of Hormuz and start_date seven days ago, then call GET /api/v1/events/{eventId}/thread for the highest-severity result

Satellite collection planning for an event

After a flood or strike, a team needs to know whether free imagery already covers it and when the next look will be. GET /api/v1/collection/plan takes an event_id and an analysis_goal of damage_assessment, flood_mapping, or wildfire_assessment and searches sentinel-1-grd and sentinel-2-l2a once each. GET /api/v1/passes then returns access windows over the target point, and GET /api/v1/imagery lists matching scene metadata with cloud_cover_max as a filter.

Call GET /api/v1/collection/plan with the event_id and analysis_goal 'flood_mapping', then GET /api/v1/passes with the event's lat and lon to list the next passes

Change measurement over an area

To answer 'how has this place changed since a given year', POST /api/v1/index-series measures a spectral index such as ndvi, ndwi, or nbr over a polygon scene by scene through the Sentinel-2 archive between start and end dates, charging only for scenes actually measured. POST /api/v1/monitoring fixes a bbox and a metric so every new acquisition is measured automatically, and GET /api/v1/monitoring/{areaId} returns the full series with anomaly flags.

POST /api/v1/index-series with a polygon, index 'nbr', start '2024-01-01', and end '2025-12-31', then report the scenes where the value dropped most

Watchlist with Slack or Discord alerts

A small team keeps watch on events and facilities without checking the app. POST /api/v1/watches adds a target with target_type event, area, or site, and notifications of what changed are listed by GET /api/v1/notifications. A connected Slack or Discord channel receives the same updates, and POST /api/v1/watches/{watchId}/notes keeps an analyst ledger of notes and judgments on each watch.

POST /api/v1/watches with target_type 'site' and the entity_id of a port from GET /api/v1/entities, then list unread items from GET /api/v1/notifications with unread_only true

Key Endpoints

51 endpoints — the off-nadir delta api returns geolocated world event signals, the changes recorded about them, and the satellite data needed to check them from orbit.

METHOD

PATH

DESCRIPTION

GET

/api/v1/signals

Query geolocated world event signals

GET

/api/v1/events/{eventId}/thread

Get one event end to end

GET

/api/v1/imagery

Search satellite scene metadata

GET

/api/v1/collection/plan

Plan imagery for one event

GET

/api/v1/passes

Predict satellite passes over a target

POST

/api/v1/index-series

Measure a spectral index over an area

POST

/api/v1/watches

Add a target to the Watchlist

GET

/api/v1/brief

Fetch the World Brief

GET

/api/v1/signals

Query geolocated world event signals

GET

/api/v1/events/{eventId}/thread

Get one event end to end

GET

/api/v1/imagery

Search satellite scene metadata

GET

/api/v1/collection/plan

Plan imagery for one event

GET

/api/v1/passes

Predict satellite passes over a target

POST

/api/v1/index-series

Measure a spectral index over an area

POST

/api/v1/watches

Add a target to the Watchlist

GET

/api/v1/brief

Fetch the World Brief

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Off-Nadir Delta by hand means choosing bearer or X-API-Key auth, tracking a token balance across metered and free routes, following cursors, and handling async analyst jobs. Through Jentic you install once, import Off-Nadir Delta from the API Directory, store the key once, and your agent calls it.

Permission scoping

Off-Nadir Delta puts the watch id in the URL path (/api/v1/watches/{watchId}), so a rule can pin your agent to one watch and the operations you pick on it. You choose the operations, so destructive ones like deleting a watch or disconnecting the notification channel are not included unless you add them.

Credential isolation

Your Off-Nadir Delta key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'predict satellite passes' or 'query world event signals', and Jentic returns the matching Off-Nadir Delta operation with its input schema, including bbox and date parameters, so the agent calls the right route directly.

FAQs

Specific to using Off-Nadir Delta API through Jentic.

What authentication does the Off-Nadir Delta API use?

Per its OpenAPI spec, the Off-Nadir Delta API accepts an API key either as a bearer token in the Authorization header, with keys starting ond_, or in the X-API-Key header. What a call returns follows the key owner's plan, and metered calls spend that key's token balance. Through Jentic the key is stored by your own instance and attached at call time.

Can I find out whether an event can be seen from satellite imagery?

Yes. GET /api/v1/collection/plan takes an event_id and an analysis_goal of damage_assessment, flood_mapping, or wildfire_assessment and searches Sentinel-1 SAR and Sentinel-2 optical collections for the event. GET /api/v1/passes predicts upcoming access windows over a point, and GET /api/v1/collection/observability surveys which events in a window a given sensor can resolve.

What are the rate limits for the Off-Nadir Delta API?

The OpenAPI spec does not state request rate limits. Usage is metered in tokens instead: each operation's description states its cost, many routes are free, and GET /api/v1/usage returns the remaining balance and plan capabilities so an agent can check before a metered call.

Is there an Off-Nadir Delta MCP server?

Yes. Off-Nadir Delta describes an MCP server at /api/v1/mcp that serves a conversational subset of the API as tools. You can also connect it directly through Jentic: your agent gets the full 51-endpoint surface from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

How do I query signals for an area through Jentic?

Search Jentic for 'query geolocated world event signals', load the querySignals operation, and execute it with a bbox, a start_date and end_date, and optional categories or min_severity_band. Follow meta.next_cursor to page through every match. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does deleting a watch remove its monitored areas?

Yes. DELETE /api/v1/watches/{watchId} removes the watch and its underlying resources, including bound monitored areas with their measurement history and standing orders. To stop a watch without losing anything, PATCH it with status set to paused, which also pauses the bound measurements and checks.

Can I limit what my agent is allowed to do with the Off-Nadir Delta API?

Yes. Write a rule that allows only GET on /api/v1/watches/{watchId} and POST on /api/v1/watches/{watchId}/notes for one watch id, and the agent can read that watch and add notes to it but cannot delete it, touch other watches, or run metered signal queries, and every call it makes is logged.

Off-Nadir Delta API

AI ReadinessNon-Ready (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationMappingbearer, apiKey51 EndpointsREST

For Agents

Query geolocated world event signals, check satellite anomalies and imagery over an area, predict satellite passes, and keep a Watchlist of events and places with notifications.

Use for: Find all signals inside this bounding box from the last week, Get the full thread for an event to see if it is new or an update, Check whether Sentinel-2 imaged this area after the event, Predict the next satellite passes over these coordinates

Not supported: Does not task commercial satellites, sell imagery bytes, or provide turn-by-turn routing or geocoding of street addresses. Use for event signals, satellite checks, and watchlists over places and areas only.

The Off-Nadir Delta API returns geolocated world event signals, the changes recorded about them, and the satellite data needed to check them from orbit. It queries Delta Signals by bounding box, date window, category, and severity band, follows an event's full thread and related events, and reports satellite-measured anomalies such as thermal hotspots, night-light drops, SO2 plumes, and ship transits at straits and canals. For imaging, it searches Sentinel-1, Sentinel-2, and NISAR scenes, plans collection for one event, predicts satellite passes over a target, measures spectral indices over a polygon, counts vessels in a SAR scene, and reads terrain elevation. A Watchlist, monitored areas, standing orders, notifications, and the daily World Brief keep an analyst current.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

71%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

82%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

45%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

40%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Off-Nadir Delta API to your agent

Capabilities

Start building with Off-Nadir Delta API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Off-Nadir Delta API

Jentic AI Readiness Score

Off-Nadir Delta API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness