API Ninjas MCP integration for AI agents.
Connect AI agents to API Ninjas through 6 structured actions, including air quality, geocode, and reverse geocode. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the API Ninjas integration exposes
The API Ninjas Agent App exposes 6 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent fetch current air quality metrics for coordinates or a city-based lookup, convert a city name into geographic coordinates and country information, and resolve latitude and longitude coordinates into place metadata. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected API Ninjas account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real API Ninjas capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
air_qualityREVIEWFetch current air quality metrics for coordinates or a city-based lookup.
INPUTS: lat / lon / city / state / country
geocodeREVIEWConvert a city name into geographic coordinates and country information.
INPUTS: city / state / country / zipcode
reverse_geocodeREVIEWResolve latitude and longitude coordinates into place metadata.
INPUTS: lat / lon
timezoneREVIEWFetch timezone metadata by timezone name or premium location lookup fields.
INPUTS: timezone / lat / lon / city / state
weatherREVIEWFetch the current weather conditions for a set of coordinates.
INPUTS: lat / lon
weather_forecastREVIEWFetch forecast weather readings for a set of coordinates.
INPUTS: lat / lon
INPUT CONTRACTS
Know what the action needs before it runs.
air_quality
latOPTIONAL- Latitude coordinate in decimal degrees between -90 and 90.
lonOPTIONAL- Longitude coordinate in decimal degrees between -180 and 180.
cityOPTIONAL- City name used to look up the requested location.
stateOPTIONAL- State or province used to narrow the city-based lookup.
countryOPTIONAL- Country name or ISO country code used to narrow the city-based lookup.
geocode
cityREQUIRED- City name to convert into geographic coordinates.
stateOPTIONAL- State or province used to narrow the city-based lookup.
countryOPTIONAL- Country name or ISO country code used to narrow the city-based lookup.
zipcodeOPTIONAL- ZIP or postal code used to narrow the geocoding lookup.
reverse_geocode
latREQUIRED- Latitude coordinate in decimal degrees between -90 and 90.
lonREQUIRED- Longitude coordinate in decimal degrees between -180 and 180.
timezone
timezoneOPTIONAL- IANA timezone identifier used by the free-tier lookup path.
latOPTIONAL- Latitude coordinate in decimal degrees between -90 and 90.
lonOPTIONAL- Longitude coordinate in decimal degrees between -180 and 180.
cityOPTIONAL- City name used to look up the requested location.
stateOPTIONAL- State or province used to narrow the city-based lookup.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Air Quality
Fetch current air quality metrics for coordinates or a city-based lookup. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
air_qualityVerify with Geocode
Convert a city name into geographic coordinates and country information. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
geocodeSAFETY BOUNDARY
Operate API Ninjas with explicit limits
- Authorize API Ninjas with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned API Ninjas data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in API Ninjas rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the API Ninjas task completed successfully.
CONNECTION MODEL
API key
API Ninjas API key used with the X-Api-Key header. Sign up for a key or find it from the official API docs: https://api-ninjas.com/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 6
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by API Ninjas.