canonical: https://jentic.com/apis/invokely.ai/invokely # Invokely statistics API The Invokely statistics API returns official statistics with units, periods, normalized places, and citable sources. It lets you search indicators, resolve place names, read a single value or a full time series, and compare or rank places on a chosen indicator. Series can be exported as CSV, and a workspace stores charts, tables, and datasets for reuse. ## For AI agents Search statistical indicators, resolve places, read single values and time series, compare and rank places, and export series as CSV. ## Scope Does not handle raw data ingestion, dashboard hosting, or user account management. Use for querying statistical indicators and time series only. ## Capabilities - Search statistical indicators by keyword - Resolve a place name to a normalized location for querying - Read a single indicator value or a full time series for a place - Compare and rank places on a chosen indicator - Export a time series as CSV for downstream analysis - Save charts, tables, and datasets to a workspace for reuse ## Use cases ### AI Agent Statistical Lookup An AI agent connected through Jentic answers data questions by resolving the place a user names, searching for the right indicator, and reading its latest value with the unit, period, and source attached. Normalized places and citable sources mean the agent returns an answer it can attribute rather than a bare number. Example prompt: Resolve the place 'Germany', then search for a population indicator and read its latest value with the source ### Time-Series Analysis and Export An analyst's agent pulls the full history of an indicator for a place and exports it as CSV for charting or modelling elsewhere. The series operation returns normalized periods so the exported data lines up across indicators. Example prompt: Retrieve a ten-year time series for an indicator and export it as CSV ### Place Comparison and Ranking To benchmark locations, an agent compares several places on one indicator and ranks a list by it, returning an ordered result with values and sources. This turns a comparison question into a single structured response. Example prompt: Compare two countries on an indicator and rank a provided list of places by the same indicator ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/indicators` | Search indicators | | GET | `/api/v1/value` | Get one indicator value | | GET | `/api/v1/series` | Get a time series | | GET | `/api/v1/compare` | Compare places on an indicator | | GET | `/api/v1/rank` | Rank places by an indicator | | GET | `/api/v1/export.csv` | Export a series as CSV | | GET | `/api/v1/catalog` | List every indicator | ## Key resources - **Indicators** — Search indicators and read their definitions - **Values** — Read single values, time series, comparisons, and rankings - **Places** — Resolve place names to normalized locations - **Workspace** — Save and manage charts, tables, and datasets - **Sources** — List data sources, licenses, and status ## 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:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 84 / 100 - **View full report:** https://jentic.com/apis/invokely.ai/invokely/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 ``` ## Why Jentic - **Setup:** Wiring the Invokely statistics API by hand means handling its bearer API key or `x-api-key` header, tracking which endpoints are free versus plan-gated, and shaping each indicator query yourself. Through Jentic you install once, import Invokely from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Invokely carries indicator and place selections in query parameters, so rules bound which operations your agent may call, not which indicators it reads. You choose the operations it may use, such as searching indicators and reading values, so the workspace save and delete operations are not included unless you add them. - **Credential handling:** Your Invokely 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. - **Discovery method:** Agents search Jentic by intent such as 'look up a statistic' or 'compare two places', and Jentic returns the matching Invokely operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Alpha Vantage** — Alpha Vantage serves economic indicators and financial time series via API. - **Data.gov** — Data.gov exposes open government datasets behind Invokely's curated indicators. - **Nasdaq Data Link** — Nasdaq Data Link adds market and alternative datasets alongside statistics. ## FAQ ### What authentication does the Invokely statistics API use? The data endpoints authenticate with an API key sent as a bearer token or in the `x-api-key` header, as declared in its OpenAPI spec. The catalog, indicator-definition, and sources endpoints are open and need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time. ### Can I compare two places on the same indicator with the Invokely statistics API? Yes. The compare operation returns values for several places on one indicator, the rank operation orders a list of places by it, and the series operation returns the full history for a single place. ### What are the rate limits for the Invokely statistics API? The OpenAPI spec does not state fixed rate limits; free keys receive a plan-required response on paid data endpoints and can use the open catalog and definition endpoints instead. Check the Invokely documentation at https://invokely.ai for the limits on your plan. ### Can I limit what my agent is allowed to do with the Invokely statistics API? Yes. Write a rule that allows only the read operations such as searching indicators, reading values, and comparing places, so the agent can query data but cannot save or delete workspace items, and every call it makes is logged. ### How do I look up a statistic with the Invokely statistics API through Jentic? Search Jentic for 'look up a statistic', add the Invokely statistics API from the directory, and store your API key once. Your agent resolves the place, searches for the indicator, and reads the value with its source. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an Invokely statistics API MCP server? You don't need an MCP server to give your agent the Invokely statistics API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the indicator, value, series, and comparison operations. That keeps extra tool definitions out of the agent's context.