Install Jentic One Beta

Connect the Latitude to your agent

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

List and filter project traces, read a trace with its spans, annotations, and memory changes, and export traces asynchronously

Break down tool-call usage with histograms, parameter stats, co-occurring tools, error breakdowns, and recent calls per toolName

Create signals backed by a judge LLM detector or a deterministic rule, then resolve, ignore, mute, or monitor them and read their trend and traces

Create monitors, list the incidents they raise, mute them, and resolve incidents

GET STARTED

Start building with Latitude API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Latitude API for, with concrete tasks.

★ Debugging a Failing Agent Tool

When a production agent starts misbehaving, a debugging agent pulls the project's tools with usage metrics, reads the error breakdown and recent errorsOnly calls for the suspect toolName, and opens the traces and spans behind them. Parameter stats and co-occurrence data show which inputs and neighbouring tools are involved, so the root cause is found from real calls rather than guesses.

Call GET /v1/projects/{projectSlug}/tools/{toolName}/errors for toolName 'search_orders' with fromIso and toIso for the last 24 hours, then GET /v1/projects/{projectSlug}/tools/{toolName}/calls with errorsOnly true and open the first trace's spans

Signal and Incident Triage

Latitude groups recurring problems into signals and raises incidents from monitors. A triage agent lists active signals sorted by recency, reads each signal's trend and example traces, resolves those fixed in the latest release, mutes noisy ones, and resolves incidents once the underlying signal is handled.

Call GET /v1/projects/{projectSlug}/signals with lifecycleGroup 'active', read GET /v1/projects/{projectSlug}/signals/{signalSlug}/trend for each, then POST /v1/projects/{projectSlug}/signals/resolve for the ones fixed

Building Regression Datasets from Production

Failures seen in production become test cases. The agent creates a dataset, imports rows from the failing traces by explicit ids or a filter set, and adds or reorders columns, giving the team a reusable set of real failure cases to check a prompt or model change against. Saved searches keep the trace filters reusable.

Call POST /v1/projects/{projectSlug}/datasets to create 'refund-failures', then POST /v1/projects/{projectSlug}/datasets/{datasetSlug}/rows/import/traces with traces set to the failing trace ids, then GET /v1/projects/{projectSlug}/datasets/{datasetSlug}/rows to confirm the import

AI Agent Self-Monitoring via Jentic

A coding or operations agent reads Latitude through Jentic without holding the organization-scoped key. It searches by intent, receives the trace, signal, or Agent Score operation with its input schema, and executes with the bearer key injected at run time, so checking production health is one step in its own release workflow.

Search Jentic for 'get the agent score for a project', load the GET /v1/projects/{projectSlug}/agent-score schema, and execute it, then call the causes operation for the same projectSlug

Key Endpoints

139 endpoints — the latitude api exposes latitude's open-source ai agent monitoring platform: it lists and inspects the traces, spans, and sessions your agents produce, breaks down tool-call usage, errors, and parameters, and tracks end users and memory stores the agent touched.

METHOD

PATH

DESCRIPTION

POST

/v1/projects/{projectSlug}/traces/list

List project traces

GET

/v1/projects/{projectSlug}/traces/{traceId}/spans

List trace spans

GET

/v1/projects/{projectSlug}/tools/{toolName}/errors

Get tool error breakdown

GET

/v1/projects/{projectSlug}/signals

List project signals

POST

/v1/projects/{projectSlug}/signals/resolve

Resolve signals

POST

/v1/projects/{projectSlug}/monitors

Create monitor

POST

/v1/projects/{projectSlug}/scores

Create project score

GET

/v1/projects/{projectSlug}/agent-score

Get Agent Score

POST

/v1/projects/{projectSlug}/traces/list

List project traces

GET

/v1/projects/{projectSlug}/traces/{traceId}/spans

List trace spans

GET

/v1/projects/{projectSlug}/tools/{toolName}/errors

Get tool error breakdown

GET

/v1/projects/{projectSlug}/signals

List project signals

POST

/v1/projects/{projectSlug}/signals/resolve

Resolve signals

POST

/v1/projects/{projectSlug}/monitors

Create monitor

POST

/v1/projects/{projectSlug}/scores

Create project score

GET

/v1/projects/{projectSlug}/agent-score

Why Jentic?

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

Setup

Wiring Latitude by hand means attaching an organization-scoped bearer key, resolving project slugs, and paging through cursor-based trace, signal, and dataset lists. Through Jentic you install once, import Latitude from the API Directory, store the key once, and your agent calls it.

Permission scoping

Latitude puts the project slug in the URL path (/v1/projects/{projectSlug}/...), so a rule can pin your agent to one project and the operations you pick. You choose that set, so destructive ones like project deletion or API key revocation are not included unless you add them.

Credential isolation

Your Latitude API 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 'find failing tool calls' or 'list open signals', and Jentic returns the matching Latitude operation with its input schema so the agent calls the right endpoint among Latitude's operations without browsing the reference docs.

FAQs

Specific to using Latitude API through Jentic.

What authentication does the Latitude API use?

Per its OpenAPI spec, the Latitude API uses the ApiKeyAuth scheme: an organization-scoped API key sent as Authorization: Bearer. The health check, the OAuth protected resource metadata, and the temporary account bootstrap endpoint need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Can I see which agent tools are failing with the Latitude API?

Yes. The tools operations list each tool with usage metrics and, per toolName, return an error breakdown, a histogram that can be limited with errorsOnly, parameter stats, co-occurring tools, and recent calls. All accept fromIso and toIso to set the time window.

What are the rate limits for the Latitude API?

The OpenAPI spec does not specify rate limits. Check https://docs.latitude.so for current limits.

How do I triage signals through Jentic with the Latitude API?

Search Jentic for 'list open signals for a project' and it returns the signals list operation with its input schema. Execute GET /v1/projects/{projectSlug}/signals, then call the resolve, ignore, or mute operations for the signals you handle. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Latitude MCP server?

You don't need an MCP server to give your agent the Latitude API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so the agent does not carry tool definitions for all of Latitude's operations in its context.

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

Yes. Write a rule that allows only the GET trace, tool, and signal reads under one projectSlug, and the agent can investigate that project's production failures while it cannot delete datasets, revoke API keys, or remove members. Every call runs through your own instance and is logged.

Latitude So Latitude

AI ReadinessNon-Ready (C-)51/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer139 EndpointsREST

For Agents

Query an AI agent's production traces, tool calls, sessions, and memory in Latitude, triage the failure signals and incidents it raises, and score, annotate, or turn traces into datasets.

Use for: Show me the traces where the search tool errored yesterday, Which tools fail most often in my production agent?, List the open signals for the support-bot project, Resolve the signals we fixed in the last release

Not supported: Does not handle running LLM inference, hosting the agent itself, or general application error tracking outside agent traces. Use for monitoring, triaging, and evaluating AI agent behaviour recorded in Latitude only.

The Latitude API exposes Latitude's open-source AI agent monitoring platform: it lists and inspects the traces, spans, and sessions your agents produce, breaks down tool-call usage, errors, and parameters, and tracks end users and memory stores the agent touched. Signals flag recurring failure patterns through an LLM judge or a deterministic rule, and can be resolved, ignored, muted, or monitored, while monitors raise incidents when something breaks. Teams also score and annotate traces, build datasets from traces, compare session populations in experiments, run analytics queries, and read an Agent Score with its causes and history.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

42%

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

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

Example Density

How richly the API is illustrated with examples.

Example Validity

Percentage of examples that conform to their schemas.

49%

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

65%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

72%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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: ASignals: 1

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Latitude to your agent

Capabilities

Start building with Latitude API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Latitude So Latitude

Jentic AI Readiness Score

Latitude

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