canonical: https://jentic.com/apis/swaggerhub.green-commute-bc36/green-commute-api

# Green Commute Bc36 Green Commute API

This is a Green Commute APi. The API exposes 14 endpoints.

## For AI agents

Programmatically gets list of all locations, find location by id. Covers 14 operations.

## Scope

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

## Capabilities

- gets list of all locations
- Find location by ID
- Integrate Green Commute API into automated workflows
- Query and filter Green Commute API records by parameters
- Monitor Green Commute API operational status and events

## Use cases

### Developer Tools Operations

Use the Green Commute API to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including gets list of all locations, find location by id, gets list of all companys.

Example prompt: Call GET /locations to gets list of all locations

### Automated location Management

Automate location operations by combining multiple Green Commute API endpoints. Agents can find location by id and then gets list of all companys in a single workflow.

Example prompt: Call GET `/locations/{locationId}` to find location by id, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'gets list of all locations', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/locations` | gets list of all locations |
| GET | `/locations/{locationId}` | Find location by ID |
| GET | `/companies` | gets list of all companys |
| GET | `/companies/{companyId}` | Find company by ID |
| GET | `/skills` | gets list of all skills |
| GET | `/skills/{skillId}` | Find skill by ID |
| GET | `/jobs` | gets list of all jobs |
| GET | `/jobs/{jobId}` | Find job by ID |

## Key resources

- **location** — Operations related to location
- **apply job** — Operations related to apply job
- **company** — Operations related to company
- **job** — Operations related to job
- **save job** — Operations related to save job

## Why Jentic

- **Setup:** Wiring the Green Commute API by hand means coding each read call against the service host and handling pagination and retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Green Commute API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the resource id in the URL path (`/jobs/{jobId}`, `/companies/{companyId}`), so a rule can pin your agent to one job or company: it can read that resource and nothing else. The operations here are all reads, and you choose which of them the agent may call.
- **Credential handling:** This Green Commute API declares no credential, so there is nothing to store. If your deployment later requires one, your own Jentic One instance stores it encrypted and injects it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list all locations' or 'get a job by id', and Jentic returns the matching Green Commute 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 Green Commute API use?

The Green Commute API uses no 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 gets list of all locations with the Green Commute API?

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

### What are the rate limits for the Green Commute 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 gets list of all locations through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets list of all locations'. Jentic returns the matching Green Commute API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Green Commute API have?

The Green Commute API exposes 14 endpoints covering location, apply job, company operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Green Commute API operations and credentials the agent may use. Every operation here is read-only (endpoints like GET /locations, GET `/jobs/{jobId}`, and GET `/companies/{companyId}`), so you can allow only the specific reads the agent needs and block the rest. Since the resource id sits in the URL path, a rule can pin the agent to a single job or company, letting it read that one resource and nothing else.