Install Jentic One Beta

Connect the Rubbish API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rubbish API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frubbish.love%2Frubbish-love" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frubbish.love%2Frubbish-love" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Rubbish API.

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

GET STARTED

Start building with Rubbish API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'get all rubbish submissions', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — rubbish provides apis for accessing litter and cleanup data.

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

GET

/api/submissions

Get all rubbish submissions

GET

/api/runs

Get all runs

GET

/api/runs/{runId}

Get movement information about a specific run

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Rubbish API through Jentic.

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.

Rubbish Love Rubbish API

Name: Rubbish API
Brand: Rubbish API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Community OpenAPI document · agent-readyHR recruitingRecruiting Atsnone3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to all rubbish submissions, I want to all runs, Search for movement information about a specific run, List all records from Rubbish API

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Rubbish API to your agent

Capabilities

Start building with Rubbish API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rubbish Love Rubbish API

Jentic AI Readiness Score

Rubbish API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness