South Pole Emissions API

Setup

Wiring the South Pole Emissions API by hand means exchanging credentials at its token endpoint for a bearer token, pointing at the api.southpole.com host, and handling the request-then-poll pattern on its sea and rail distance calls yourself. Through Jentic you install once, import the South Pole Emissions API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The South Pole Emissions API takes its calculation inputs in the request body rather than resource ids in the URL path, so limit the agent to the operations it needs, such as calculating flight emissions or hotel emissions. You choose which operations are in the allowed set, so anything you do not add stays out of reach.

Credential isolation

Your South Pole credential 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 'calculate flight emissions' or 'calculate hotel emissions', and Jentic returns the matching South Pole Emissions API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.