Terrascope Be Terrascope OpenSearch API

Name: Terrascope OpenSearch API
Brand: Terrascope OpenSearch API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontnone3 EndpointsREST

For Agents

Programmatically retrieve opensearch description document (osdd), search for available eo data collections. Covers 3 operations.

Install Jentic One Beta

Connect the Terrascope OpenSearch API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Terrascope OpenSearch 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%2Fterrascope.be%2Fterrascope-be" | 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%2Fterrascope.be%2Fterrascope-be" | 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 Terrascope OpenSearch API.

Retrieve OpenSearch Description Document (OSDD)

Search for available EO data collections

Integrate Terrascope OpenSearch API into automated workflows

GET STARTED

Start building with Terrascope OpenSearch API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Terrascope OpenSearch API for, with concrete tasks.

★ E-Commerce Operations

Use the Terrascope OpenSearch API to perform e commerce operations programmatically. The API provides 3 endpoints covering core functionality including retrieve opensearch description document (osdd), search for available eo data collections, search for products within a specific collection.

Call GET /description to retrieve opensearch description document (osdd)

Automated Collections Management

Automate collections operations by combining multiple Terrascope OpenSearch API endpoints. Agents can search for available eo data collections and then search for products within a specific collection in a single workflow.

Call GET /collections to search for available eo data collections, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Terrascope OpenSearch 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 none tokens manually.

Search Jentic for 'retrieve opensearch description document (osdd)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — opensearch-based catalogue api for discovering earth observation data collections and products on the terrascope platform.

METHOD

PATH

DESCRIPTION

GET

/description

Retrieve OpenSearch Description Document (OSDD)

GET

/collections

Search for available EO data collections

GET

/products

Search for products within a specific collection

GET

/description

Retrieve OpenSearch Description Document (OSDD)

GET

/collections

Search for available EO data collections

GET

/products

Search for products within a specific collection

Why Jentic?

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

Setup

Wiring the Terrascope OpenSearch API by hand means pointing at the services.terrascope.be/catalogue host and coding its description, collection, and product queries yourself. Through Jentic you install once, import the Terrascope OpenSearch API from the API Directory, store any required credential once, and your agent calls it.

Permission scoping

The Terrascope OpenSearch API exposes read-only catalogue queries with parameters in the query string rather than a resource id in the URL path, so limit the agent to the operations it needs, such as searching products or listing collections. You choose the operations it may call, so it reads only the catalogue endpoints you allow.

Credential isolation

Any credential for the Terrascope OpenSearch API 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 'search the product catalogue' or 'list available collections', and Jentic returns the matching Terrascope OpenSearch API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Terrascope OpenSearch API through Jentic.

What authentication does the Terrascope OpenSearch API use?

The Terrascope OpenSearch API uses no 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 retrieve opensearch description document (osdd) with the Terrascope OpenSearch API?

Yes. Use the GET /description endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Terrascope OpenSearch 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 retrieve opensearch description document (osdd) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve opensearch description document (osdd)'. Jentic returns the matching Terrascope OpenSearch API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Terrascope OpenSearch API have?

The Terrascope OpenSearch API exposes 3 endpoints covering collections, description, products operations.