What are the rate limits for the Geo-Parity API?

The OpenAPI spec notes that keyless callers get a monthly allowance per IP plus a per-minute burst cap, and an optional key raises both. The datasets endpoint reports every dataset and when it last changed, which helps an agent pace freshness checks. See https://geo-parity.com for current limits.

Can I compare the cost of living between countries with the Geo-Parity API?

Yes. GET /api/compare.json compares two countries across all datasets, GET /api/total-cost.json weighs total monthly cost against a stated income, and GET /api/salary.json localizes a salary using purchasing power parity. The dossier endpoint pulls one country's headline figures with the source of each.

Is there a Geo-Parity MCP server?

You don't need an MCP server to give your agent Geo-Parity. Jentic connects it directly from the API Directory: import it and your agent calls the cost-of-living, visa, and comparison operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

How do I localize a salary with the Geo-Parity API through Jentic?

Search Jentic for 'localize a salary to a target country', and it returns the Geo-Parity salary operation with its input schema. Load it and execute GET /api/salary.json, with an optional key injected at run time if a higher quota is needed. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Geo-Parity API?

Yes. Because the datasets are read through separate operations, write a rule that allows only the reads a task needs, for example the cost-of-living comparison and salary localization, so the agent cannot create or revoke API keys or reach unrelated datasets. Because every call runs through your own instance, each one is logged for you to review.