canonical: https://jentic.com/apis/skoot.eco/skoot-eco

# SkootEco API

SkootEco is an accredited climate platform that lets you plant trees, recover plastic, buy carbon offset, and showcase your climate impact. The API exposes 3 endpoints secured with bearer authentication.

## For AI agents

Programmatically validate API token, get profile by id. Covers 3 operations with bearer authentication.

## Scope

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

## Capabilities

- Validate API token
- Get profile by ID
- Make an allocation
- Query and filter SkootEco API records by parameters
- Monitor SkootEco API operational status and events

## Use cases

### Developer Tools Operations

Use the SkootEco API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including validate API token, get profile by id, make an allocation.

Example prompt: Call GET `/api/key/validate` to validate API token

### Automated Authentication Management

Automate authentication operations by combining multiple SkootEco API endpoints. Agents can get profile by id and then make an allocation in a single workflow.

Example prompt: Call GET `/profile/{profileId}` to get profile by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SkootEco 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 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/key/validate` | Validate API token |
| GET | `/profile/{profileId}` | Get profile by ID |
| PATCH | `/profile/{profileId}/allocate` | Make an allocation |

## Key resources

- **Authentication** — API key validation
- **Profiles** — Profile and allocation operations

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/skoot.eco/skoot-eco/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 SkootEco by hand means sending a bearer token in the Authorization header to api.skoot.eco, validating the key, and handling the profile read and allocate calls yourself. Through Jentic you install once, import SkootEco from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** SkootEco puts the profile id in the URL path (`/profile/{profileId}` and `/profile/{profileId}/allocate`), so a rule can pin your agent to one profile. You choose the operations it may call, so if you only grant reading a profile, the allocate operation is not included unless you add it.
- **Credential handling:** Your SkootEco bearer token 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 'validate my key' or 'allocate against a profile', and Jentic returns the matching SkootEco 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 SkootEco API use?

The SkootEco API uses a Bearer token in the Authorization 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 validate API token with the SkootEco API?

Yes. Use the GET `/api/key/validate` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SkootEco 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 validate API token through Jentic?

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

### How many endpoints does the SkootEco API have?

The SkootEco API exposes 3 endpoints covering authentication, profiles operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which SkootEco operations and credentials your agent may use. You choose the operations it may call, so you can grant read-only access to GET `/profile/{profileId}` and leave the PATCH `/profile/{profileId}/allocate` operation out unless you add it. Because SkootEco carries the profile id in the URL path, a rule can also pin the agent to a single profile.