canonical: https://jentic.com/apis/southpole.com/southpole

# South Pole Emissions API

South Pole API for calculating carbon emissions from flights, hotels, and freight transport distances. Provides emissions calculation and distance measurement services. The API exposes 14 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically get access token, calculate flight emissions (v1). Covers 14 operations with bearer, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Get access token
- Calculate flight emissions (v1)
- Create sea distance request
- Query and filter South Pole Emissions API records by parameters
- Monitor South Pole Emissions API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the South Pole Emissions API to perform maps geolocation operations programmatically. The API provides 14 endpoints covering core functionality including get access token, calculate flight emissions (v1), calculate flight emissions (v2).

Example prompt: Call POST /token to get access token

### Automated Authentication Management

Automate authentication operations by combining multiple South Pole Emissions API endpoints. Agents can calculate flight emissions (v1) and then calculate flight emissions (v2) in a single workflow.

Example prompt: Call POST /calculateflightemissions to calculate flight emissions (v1), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call South Pole Emissions API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Example prompt: Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/token` | Get access token |
| POST | `/calculateflightemissions` | Calculate flight emissions (v1) |
| POST | `/calculateflightsemissionsrdc` | Calculate flight emissions (v2) |
| POST | `/calculatehotelsemissions` | Calculate hotel emissions |
| POST | `/createseadistancerequest` | Create sea distance request |
| GET | `/getseadistanceresponse` | Get sea distance response |
| POST | `/createraildistancerequest` | Create rail distance request |
| GET | `/getraildistanceresponse` | Get rail distance response |

## Key resources

- **Authentication** — Token management
- **Emissions Calculations** — Calculate carbon emissions for flights and hotels
- **Distance Calculations** — Calculate freight transport distances by sea, rail, road, and air
- **Location Datasets** — Retrieve airport and location code datasets

## 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:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 80 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/southpole.com/southpole/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the South Pole Emissions API use?

The South Pole Emissions API uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get access token with the South Pole Emissions API?

Yes. Use the POST /token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the South Pole Emissions API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching South Pole Emissions API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the South Pole Emissions API have?

The South Pole Emissions API exposes 14 endpoints covering authentication, emissions calculations, distance calculations operations.

### Can I limit what my agent is allowed to do with the South Pole Emissions API?

Yes. Jentic One is self-hosted by you, so your own rules decide which South Pole Emissions API operations and credentials the agent may use. You add only the operations the agent needs, such as calculating flight emissions or hotel emissions, and leave out the sea and rail distance calls or the token exchange if they are not required. Because the API takes its calculation inputs in the request body rather than resource ids in the URL, anything you do not put in the allowed set stays out of the agent's reach.