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

# Where to Credit API

The Where to Credit API provides mileage earning calculations for frequent flyer programs around the world. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically calculates the number of miles earned for every frequent flyer program., lists all supported frequent flyer programs.. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Calculates the number of miles earned for every frequent flyer program.
- Lists all supported frequent flyer programs.
- Integrate Where to Credit API into automated workflows
- Query and filter Where to Credit API records by parameters
- Monitor Where to Credit API operational status and events

## Use cases

### Developer Tools Operations

Use the Where to Credit API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including calculates the number of miles earned for every frequent flyer program., lists all supported frequent flyer programs..

Example prompt: Call POST `/api/1.0/calculate` to calculates the number of miles earned for every frequent flyer program.

### Data Retrieval and Monitoring

Query Where to Credit API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Where to Credit API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Where to Credit 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 apiKey tokens manually.

Example prompt: Search Jentic for 'calculates the number of miles earned for every frequent flyer program.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/1.0/calculate` | Calculates the number of miles earned for every frequent flyer program. |
| GET | `/api/1.0/programs` | Lists all supported frequent flyer programs. |

## Key resources

- **1.0** — Operations for 1.0

## 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:** 52 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 30 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 56 / 100
- **View full report:** https://jentic.com/apis/wheretocredit.com/wheretocredit/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 Where to Credit API by hand means placing its API key in the Authorization-Token header on every request and handling retries yourself. Through Jentic you install once, import the Where to Credit API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Where to Credit API carries its inputs in the request body and query rather than in the path, so limit the agent to the operations it needs, such as listing programs. You choose the operations it may call, so the mileage calculation is not included unless you add it.
- **Credential handling:** Your Where to Credit 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 'list frequent flyer programs' or 'calculate miles earned', and Jentic returns the matching Where to Credit API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Where to Credit API use?

The Where to Credit API uses an API key passed in the `Authorization-Token` header. 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 calculates the number of miles earned for every frequent flyer program. with the Where to Credit API?

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

### What are the rate limits for the Where to Credit 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 calculates the number of miles earned for every frequent flyer program. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'calculates the number of miles earned for every frequent flyer program.'. Jentic returns the matching Where to Credit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Where to Credit API have?

The Where to Credit API exposes 2 endpoints covering 1.0 operations.

### Can I limit what my agent is allowed to do with the Where to Credit API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Where to Credit API's two operations the agent may call. You can allow it to list supported programs with GET `/api/1.0/programs` while withholding the mileage calculation at POST `/api/1.0/calculate`, or grant both. The stored API key is injected only for the operations you permit, so the agent never gains access to endpoints you have not enabled.