Install Jentic One Beta

Connect the Coreo API to your agent

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

List the surveys defined for a project

List and read the records collected against a project's surveys

Read UKHab baselines for a project

Read UKHab pre-surveys for a project

Read UKHab species feature notes for a project

GET STARTED

Start building with Coreo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Coreo API for, with concrete tasks.

★ Agent survey-data retrieval

An AI agent connected through Jentic lists a project's surveys and pulls the records collected against them to answer a question about field observations, without a human exporting data from Coreo. Because the agent uses a read-only key, it can read project data but cannot change it.

List the surveys for a project and retrieve the records for the chosen survey, expanding the survey and geometry

UKHab habitat reporting

Ecology consultants read a project's UKHab baselines, pre-surveys, and species feature notes to assemble a habitat report. Coreo exposes each UKHab record type as its own endpoint so an agent can gather baselines and species feature notes for one project in sequence.

Read the UKHab baselines and species feature notes for a project and compile them into a single summary

Lean-to-expanded data sync

A data pipeline first reads records in Coreo's lean form, where related objects are returned as IDs, then re-requests with the expand parameter to hydrate user, survey, and geometry only where needed. This keeps routine syncs small while still allowing full detail on demand.

Fetch a project's records in lean form, then re-fetch a single record with expand set to user, survey, and geometry

Key Endpoints

9 endpoints — the coreo api reads ecological survey data from projects on the coreo platform, returning the surveys defined for a project and the records collected against them.

METHOD

PATH

DESCRIPTION

GET

/v1/projects/{projectId}/surveys

List project surveys

GET

/v1/projects/{projectId}/records

List project records

GET

/v1/projects/{projectId}/records/{recordId}

Get a single record

GET

/v1/modules/ukhab/projects/{projectId}/baselines

List UKHab baselines

GET

/v1/modules/ukhab/projects/{projectId}/presurveys

List UKHab pre-surveys

GET

/v1/modules/ukhab/projects/{projectId}/sfns

List UKHab species feature notes

GET

/v1/projects/{projectId}/surveys

List project surveys

GET

/v1/projects/{projectId}/records

List project records

GET

/v1/projects/{projectId}/records/{recordId}

Get a single record

GET

/v1/modules/ukhab/projects/{projectId}/baselines

List UKHab baselines

GET

/v1/modules/ukhab/projects/{projectId}/presurveys

List UKHab pre-surveys

GET

/v1/modules/ukhab/projects/{projectId}/sfns

List UKHab species feature notes

Why Jentic?

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

Setup

Wiring the Coreo API by hand means issuing a read-only JWT, sending it in the Authorization header with the literal JWT prefix, and learning the expand query parameter for lean responses. Through Jentic you install once, import Coreo from the API Directory, store the token once, and your agent calls it.

Permission scoping

Coreo puts the projectId in the URL path (/v1/projects/{projectId}/...) and its keys are read-only, so a rule can pin your agent to one project. You choose the read operations it may call, so it can read that project's surveys and records and nothing on other projects unless you add them.

Credential isolation

Your Coreo token 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 'read project records' or 'read UKHab baselines', and Jentic returns the matching Coreo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Coreo API through Jentic.

What authentication does the Coreo API use?

The Coreo API authenticates with a token sent in the Authorization header, prefixed with the literal word JWT and a space, per its OpenAPI spec. API keys are read-only and must have access to the requested project. Through Jentic the token is stored once by your own self-hosted instance and injected when a call runs, so it never appears in the agent's prompt or logs.

Can I read a project's records with the Coreo API?

Yes. List the surveys for a project, then read the records collected against them, or get a single record by its id. Responses are lean by default and return related objects as IDs, so pass the expand parameter to hydrate user, survey, and geometry when you need the full objects.

Can I limit what my agent is allowed to do with the Coreo API?

Yes. The API is read-only and Coreo puts the projectId in the URL path, so a rule can pin your agent to one project and the survey and record read operations you choose, so it cannot read other projects, and every call it makes is logged.

What are the rate limits for the Coreo API?

The spec states that requests are limited per IP and per authenticated user, and that an exceeded limit returns a 429 response with a Retry-After header. Check the Coreo documentation for the current numeric limits before running large syncs.

Is there a Coreo MCP server?

You don't need an MCP server to give your agent the Coreo API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the survey and record read operations on demand without loading another server's tool definitions into its context.

How do I read survey records with the Coreo API through Jentic?

Search Jentic by intent such as 'read project survey records', and Jentic returns the records operation with its input schema so your agent passes the projectId and reads back the records. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Coreo API

AI ReadinessFoundational (D)46/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityForms SurveysapiKey9 EndpointsREST

For Agents

Read ecological project data from Coreo: a project's surveys and the records collected against them, plus UKHab baselines, pre-surveys, and species feature notes. Read-only.

Use for: List the surveys set up for this project, Retrieve the records collected for this project, Get a single record by its id, Read the UKHab baselines for this project

Not supported: Does not create surveys, write records, or render maps. Use for reading ecological project survey data, records, and UKHab modules only.

The Coreo API reads ecological survey data from projects on the Coreo platform, returning the surveys defined for a project and the records collected against them. It also exposes the UKHab habitat module, with baselines, pre-surveys, and species feature notes for a project. Responses are lean by default, returning related objects as IDs, and an expand query parameter pulls in related objects such as user, survey, and geometry in a single request. API keys are read-only and must have access to the requested project.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

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

42%

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.

50%

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: FSignals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

50%

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: C-Signals: 1

50%

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: A-Signals: 1

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Coreo API to your agent

Capabilities

Start building with Coreo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Coreo API

Jentic AI Readiness Score

Coreo 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