canonical: https://jentic.com/apis/rubbish.love/rubbish-love

# Rubbish Love Rubbish API

Rubbish provides APIs for accessing litter and cleanup data. Retrieve submissions, runs, and run movement information collected through the Rubbish platform. The API exposes 3 endpoints.

## For AI agents

Programmatically get all rubbish submissions, get all runs. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get all rubbish submissions
- Manage hr recruiting data programmatically
- Integrate Rubbish API into automated workflows
- Query and filter Rubbish API records by parameters
- Monitor Rubbish API operational status and events

## Use cases

### HR and Recruiting Operations

Use the Rubbish API to perform hr recruiting operations programmatically. The API provides 3 endpoints covering core functionality including get all rubbish submissions, get all runs, get movement information about a specific run.

Example prompt: Call GET `/api/submissions` to get all rubbish submissions

### Automated Runs Management

Automate runs operations by combining multiple Rubbish API endpoints. Agents can get all runs and then get movement information about a specific run in a single workflow.

Example prompt: Call GET `/api/runs` to get all runs, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rubbish 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 'get all rubbish submissions', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/submissions` | Get all rubbish submissions |
| GET | `/api/runs` | Get all runs |
| GET | `/api/runs/{runId}` | Get movement information about a specific run |

## Key resources

- **Runs** — Operations related to Runs
- **Submissions** — Operations related to Submissions

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rubbish.love/rubbish-love/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 Rubbish API by hand means writing your own request handling against api.rubbish.love and paging through submissions and runs yourself. Through Jentic you install once, import the Rubbish API from the API Directory, and your agent calls it.
- **Permission scoping:** Rubbish puts the run id in the URL path (`/api/runs/{runId}`), so a rule can pin your agent to one run: it can read that run's movement data and nothing else. Every operation here is read-only, so you choose which of the read endpoints the agent may call.
- **Credential handling:** The Rubbish API is called without a credential, so there is no token to manage. Jentic One still runs the call through its own instance so execution stays inside your infrastructure.
- **Discovery method:** Agents search Jentic by intent such as 'get all rubbish submissions' or 'get movement for a run', and Jentic returns the matching Rubbish operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Rubbish API use?

The Rubbish 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 get all rubbish submissions with the Rubbish API?

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

### What are the rate limits for the Rubbish 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 all rubbish submissions through Jentic?

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

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

The Rubbish API exposes 3 endpoints covering runs, submissions operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Rubbish operations the agent may call. Every endpoint here is read-only, so you can allow only the reads you want, such as GET `/api/submissions` or GET `/api/runs.` Since the run id sits in the URL path (GET `/api/runs/{runId}`), a rule can pin the agent to one run so it reads that run's movement data and nothing else.