Eckari capability API
66
AI ReadinessAI-Aware (B)66/100
Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer, apiKey24 EndpointsREST
For Agents
Call a provider-neutral set of read-only lookups: UK and US company profiles, directors, filings and charges, GLEIF legal-entity records, domain WHOIS, ECB FX reference rates, US geocoding, carrier detection, and US weather.
Use for: Search Companies House for a UK company by name, Get a UK company's directors and filing history, Profile a US public company from SEC EDGAR by ticker, Resolve a company name to its SEC CIK
Not supported: Does not create or modify records, settle payments, or store your data. Use for read-only company, entity, FX, location, and reference lookups only.
The Eckari capability API serves a provider-neutral set of read-only lookups that agents can call directly. It profiles UK companies from Companies House (directors, charges, filings, beneficial owners, and status) and US public companies from SEC EDGAR, resolves legal entities by LEI from the GLEIF register, runs domain WHOIS and RDAP checks, returns official ECB reference exchange rates, geocodes US addresses against Census TIGER data, detects parcel carriers from a tracking number, and reports US weather forecasts, observations, and alerts from the NWS.
Install Jentic One Beta
Connect the Eckari capability API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eckari capability 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.
1
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%2Feckari.com%2Feckari" | sh2
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%2Feckari.com%2Feckari" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Eckari capability API.
Search and profile UK companies from Companies House, including directors, charges, filings, and beneficial owners
Profile US public companies from SEC EDGAR and resolve a company name to its CIK and ticker
Look up legal entities by LEI from the GLEIF register
Run WHOIS and RDAP checks for domain registration and expiry
Fetch official ECB reference exchange rates for a currency pair
Geocode US addresses, detect parcel carriers, and read NWS weather forecasts, observations, and alerts
Use Cases
Patterns agents use Eckari capability API for, with concrete tasks.
★ Agent-run company due diligence
An agent researching a UK company searches Companies House by name through Eckari, pulls the company profile, then reads its directors, charges, and filing history to build a due-diligence summary. Each capability is discovered through Jentic by intent, so the agent calls the right lookup with the company number without reading the reference docs.
Search Companies House for a company by name, then retrieve its profile, directors, and latest filings and summarise the result
Entity resolution with LEI and SEC data
Resolve a counterparty to canonical identifiers by combining the GLEIF LEI lookup with SEC EDGAR profiles. An agent can take a company name, resolve it to a US CIK and ticker, and attach the matching GLEIF legal-entity record so downstream systems key on stable identifiers.
Resolve a company name to its SEC CIK and ticker, then fetch the matching GLEIF legal-entity profile by LEI
Domain, FX, and location reference checks
Enrich a record with reference data by chaining Eckari's domain, foreign-exchange, and location lookups. An agent can verify a domain's registration and expiry, convert amounts with the official ECB reference rate, and geocode a US address to coordinates and Census geographies in one pass.
Check a domain's registration and expiry, fetch the ECB reference rate for a currency pair, then geocode a US street address
US weather and logistics context
Add operational context to a workflow using the NWS weather and carrier-detection lookups. An agent can detect the carrier behind a tracking number and read the current US forecast, latest observation, and any active alerts for a set of coordinates before routing a decision.
Detect the carrier for a tracking number, then read the US forecast and active alerts for the destination coordinates
Key Endpoints
24 endpoints — the eckari capability api serves a provider-neutral set of read-only lookups that agents can call directly.
METHOD
PATH
DESCRIPTION
GET
/v1/companies/uk/search
Search Companies House for UK companies by name
GET
/v1/companies/uk/{company_number}
Get a UK company profile
GET
/v1/companies/us/{id}
US public company profile from SEC EDGAR
GET
/v1/entities/lei/{lei}
Legal entity profile by LEI from GLEIF
GET
/v1/domains/{domain}/registration
WHOIS/RDAP domain registration
GET
/v1/fx/reference-rate
ECB reference exchange rate for a pair
GET
/v1/locations/us/geocode
Geocode a US street address
GET
/v1/weather/us/forecast
US weather forecast for coordinates
GET
/v1/companies/uk/search
Search Companies House for UK companies by name
GET
/v1/companies/uk/{company_number}
Get a UK company profile
GET
/v1/companies/us/{id}
US public company profile from SEC EDGAR
GET
/v1/entities/lei/{lei}
Legal entity profile by LEI from GLEIF
GET
/v1/domains/{domain}/registration
WHOIS/RDAP domain registration
GET
/v1/fx/reference-rate
ECB reference exchange rate for a pair
GET
/v1/locations/us/geocode
Geocode a US street address
GET
/v1/weather/us/forecast
US weather forecast for coordinates
Jentic AI Readiness Score
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.
E
Eckari capability API
- AI-Aware (B)66/100
99
Foundational Compliance44
Developer Experience & Jentic Compatibility59
AI-Readiness & Agent Experience94
Agent Usability55
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
44
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: DSignals: 4
2%
Example Density
How richly the API is illustrated with examples.
0%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
59
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
63%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
72%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Eckari capability API by hand means handling its bearer account key or the x402 accountless payment flow, and normalising responses drawn from Companies House, SEC EDGAR, GLEIF, RDAP, the ECB, Census, and the NWS yourself. Through Jentic you install once, import the Eckari capability API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Eckari groups its surface into distinct capability operations like UK company lookups, US SEC profiles, LEI entity search, domain WHOIS, FX rates, geocoding, and weather, so a rule bounds which of those operations your agent may call. You choose the operations it may call, so unrelated capabilities stay off unless you add them.
Credential isolation
Your Eckari 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 'profile a UK company' or 'get the ECB reference rate', and Jentic returns the matching Eckari 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.
FAQs
Specific to using Eckari capability API through Jentic.
What authentication does the Eckari capability API use?
Per its OpenAPI spec, the Eckari capability API accepts a bearer account key (shaped ek_live_ or ek_test_) and also supports x402 accountless payment, where an unpaid request returns HTTP 402 and is retried with a PAYMENT-SIGNATURE header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I look up UK company directors with the Eckari capability API?
Yes. The UK directors operation returns the officers register for a company from Companies House, and sibling operations cover charges, filings, beneficial owners, registered office, and company status for the same company number.
What are the rate limits for the Eckari capability API?
The OpenAPI spec does not state a fixed request rate limit; usage is metered and billed in arrears per successful request. Check the Eckari documentation at https://eckari.com for current limits and per-capability pricing.
Is there an Eckari MCP server?
You don't need an MCP server to give your agent the Eckari capability API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the company, entity, FX, location, and weather lookups it needs.
Can I limit what my agent is allowed to do with the Eckari capability API?
Yes. Eckari is split into distinct capability operations, so you scope by operation: write a rule that allows just the lookups the task needs, such as UK company search and profile, and leave FX, weather, domain, and location lookups off. The agent can then call only those operations, and each request is logged.
How do I profile a company through Jentic?
Search Jentic for 'profile a UK company', and it returns the Eckari company-profile operation with its input schema; your agent supplies the company number and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED