canonical: https://jentic.com/apis/terrascope.be/terrascope-be

# Terrascope Be Terrascope OpenSearch API

OpenSearch-based catalogue API for discovering Earth Observation data collections and products on the Terrascope platform. Supports geographic, temporal, and metadata-based filtering with GeoJSON and Atom response formats. The API exposes 3 endpoints.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Retrieve OpenSearch Description Document (OSDD)
- Search for available EO data collections
- Integrate Terrascope OpenSearch API into automated workflows
- Query and filter Terrascope OpenSearch API records by parameters
- Monitor Terrascope OpenSearch API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Collections** — Operations for collections
- **Description** — Operations for description
- **Products** — Operations for products

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/terrascope.be/terrascope-be/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

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

### Can I limit what my agent is allowed to do with the Terrascope OpenSearch API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which operations and credentials your agent may use. The Terrascope OpenSearch API exposes only read-only catalogue queries, so you can allow just the GET operations the agent needs, such as searching products or listing collections, and withhold the others. This means the agent reads only the description, collection, or product endpoints you have permitted and nothing more.