Install Jentic One Beta

Connect the Jet Tracker Partner API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jet Tracker Partner 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%2Fjettracker.com.br%2Fjettracker" | 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%2Fjettracker.com.br%2Fjettracker" | 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 Jet Tracker Partner API.

Get the full profile of a Brazilian-registered aircraft by registration mark, such as PR-TBL, with GET /api/v1/aircraft/{registration}

Read an aircraft's owner set with CNPJs and company partners, its operator, lien (gravame), and flightActivity from ADS-B coverage

List every aircraft linked to a company CNPJ or 8-digit root, with role, status, segment, and co-owners, via GET /api/v1/owner/{cnpj}/aircraft

Filter a company's fleet by segment such as executive, geral, comercial, or militar

GET STARTED

Start building with Jet Tracker Partner API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jet Tracker Partner API for, with concrete tasks.

★ Aviation sales research agent through Jentic

A sales or brokerage agent researching business aviation prospects in Brazil can go from a lead's email domain to its aircraft. Through Jentic it finds each Jet Tracker operation by intent: GET /api/v1/company/search with domain returns candidate CNPJs, GET /api/v1/owner/{cnpj}/aircraft lists the fleet, and GET /api/v1/aircraft/{registration} gives each aircraft's owners, lien, and value reference. The jtpk_ partner key is injected at call time and never sits in the agent's context.

Call GET /api/v1/company/search with domain 'acme.com.br', take the top candidate's CNPJ root, then call GET /api/v1/owner/{cnpj}/aircraft with segment 'executive' and summarise the fleet

Aircraft due diligence

Before a purchase or financing deal, a buyer needs the registry picture of one aircraft. GET /api/v1/aircraft/{registration} accepts a mark with or without hyphen in any case and returns RAB status, owner set with Receita Federal records and partners, operator, lien (gravame), flight activity, and a value reference by vintage, each figure with a source and as_of date. A registry movement is not a sale, and flightActivity.tracked false means no tracking coverage, not that the aircraft does not fly.

Call GET /api/v1/aircraft/{registration} with registration 'PR-TBL' and report the owners, the lien status, and the value reference with their as_of dates

Fleet watch lists

Enterprise accounts can be alerted when watched aircraft change. PUT /api/v1/watches replaces the whole watch list idempotently with up to 500 registrations, and GET /api/v1/watches returns the registrations currently watched by the account key.

Call PUT /api/v1/watches with registrations ['PR-TBL','PP-ABC'] and confirm with GET /api/v1/watches

Key Endpoints

6 endpoints — the jet tracker partner api returns ownership and activity profiles for brazilian-registered aircraft and links them to the companies behind them.

METHOD

PATH

DESCRIPTION

GET

/api/v1/aircraft/{registration}

Full profile of a Brazilian-registered aircraft

GET

/api/v1/owner/{cnpj}/aircraft

Aircraft linked to a company CNPJ

GET

/api/v1/company/search

Candidate CNPJs for a company name or email domain

GET

/api/v1/watches

List watched registrations

PUT

/api/v1/watches

Replace the watch list

GET

/api/v1/aircraft/{registration}

Full profile of a Brazilian-registered aircraft

GET

/api/v1/owner/{cnpj}/aircraft

Aircraft linked to a company CNPJ

GET

/api/v1/company/search

Candidate CNPJs for a company name or email domain

GET

/api/v1/watches

List watched registrations

PUT

/api/v1/watches

Replace the watch list

Why Jentic?

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

Setup

Wiring Jet Tracker by hand means handling its jtpk_ bearer key, its plan-gated operations, and quota truncation on list results. Through Jentic you install once, import the Jet Tracker Partner API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Jet Tracker puts the aircraft registration and the company CNPJ in the URL path, so a rule can pin your agent to one aircraft (/api/v1/aircraft/PR-TBL) or one company's fleet. You choose the operations it may call, so watch list replacement is not included unless you add it.

Credential isolation

Your Jet Tracker partner 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 'who owns this Brazilian aircraft' or 'list a company's aircraft', and Jentic returns the matching Jet Tracker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Jet Tracker Partner API through Jentic.

Is there a Jet Tracker MCP server?

Yes - per its OpenAPI spec, Jet Tracker offers an MCP server that uses the same key and plan rules. You can also connect the Jet Tracker Partner API directly through Jentic: your agent gets the full 6-endpoint surface from the spec without loading another server's tool definitions into its context, your partner 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.

What authentication does the Jet Tracker Partner API use?

Per its OpenAPI spec, the API authenticates with a partner key (jtpk_...) generated in the Jet Tracker account and sent as a bearer token in the Authorization header. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Which Jet Tracker plan do I need?

Per the spec, looking at one aircraft is Starter, generating a list such as a CNPJ fleet is Pro, and watches are Enterprise. Plan names changed in October 2026 while the tier keys in responses did not: the key pro is the Starter plan and the key business is the Pro plan.

Can I limit what my agent is allowed to do with the Jet Tracker Partner API?

Yes. For example, write a rule that allows only GET /api/v1/aircraft/{registration} and GET /api/v1/company/search. Your agent can then look up single aircraft and resolve companies but cannot pull whole fleets or replace your watch list, and every call it makes is logged.

What are the rate limits for the Jet Tracker Partner API?

Per the OpenAPI spec, each key has daily quotas on calls, single-aircraft lookups, and records returned by lists; when one is exceeded the API answers 429 with resetAt in UTC, and list results are cut at the remaining daily records with quotaTruncated set to true. See https://jettracker.com.br/desenvolvedores for the per-plan figures.

How do I look up an aircraft's owner through Jentic?

Search Jentic for 'who owns this Brazilian aircraft', load the getAircraftByRegistration operation, and call GET /api/v1/aircraft/{registration} with the mark, with or without hyphen. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does the Jet Tracker Partner API return personal data?

Names of natural persons may appear because they are public registry data, but per the spec a CPF never does, and GET /api/v1/owner/{cnpj}/aircraft rejects a CPF in place of a CNPJ.

Jet Tracker Partner API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer6 EndpointsREST

For Agents

Look up a Brazilian aircraft's owners, operator, lien, flight activity, and value reference by registration, list the fleet tied to a company CNPJ, and resolve company names or email domains to CNPJs.

Use for: Who owns the aircraft PR-TBL?, List all aircraft owned or operated by this company CNPJ, Find the CNPJ for a company from its email domain acme.com.br, Check whether this jet has a lien on it

Not supported: Does not track live flight positions, book charters, or cover aircraft registered outside Brazil. Use for Brazilian aircraft registry, ownership, and company fleet lookups only.

The Jet Tracker Partner API returns ownership and activity profiles for Brazilian-registered aircraft and links them to the companies behind them. A registration lookup returns the RAB status, model, year, owner set with names, CNPJs, and the Receita Federal record with company partners, plus operator, owner state, lien (gravame), ADS-B flight activity, market presence, and a published value reference by vintage. A CNPJ lookup lists every aircraft tied to a company's 8-digit root, a company search turns a name or email domain into candidate CNPJs with confidence and economic group, and Enterprise accounts can maintain a watch list of up to 500 registrations. Every number carries a source and an as_of date.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

97%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

54%

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: D-Signals: 4

23%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

83%

OperationId Quality

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

58%

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

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jet Tracker Partner API to your agent

Capabilities

Start building with Jet Tracker Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jet Tracker Partner API

Jentic AI Readiness Score

Jet Tracker Partner 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