canonical: https://jentic.com/apis/rbaskets.in/rbaskets

# Rbaskets In Request Baskets API

RESTful API of [Request Baskets](https://rbaskets.in) service. Request Baskets is an open source project of a service to collect HTTP requests and inspect them via RESTful API or web UI. Check out the [project page](https://github.com/darklynx/request-baskets) for more detailed description. The API exposes 20 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get baskets, create new basket. Covers 20 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get baskets
- Create new basket
- Update basket settings
- Delete basket
- Access Request Baskets API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the Request Baskets API to perform developer tools operations programmatically. The API provides 20 endpoints covering core functionality including get baskets, create new basket, get basket settings.

Example prompt: Call GET `/api/baskets` to get baskets

### Automated service Management

Automate service operations by combining multiple Request Baskets API endpoints. Agents can create new basket and then get basket settings in a single workflow.

Example prompt: Call POST `/api/baskets/{name}` to create new basket, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Request Baskets 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 'get baskets', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/baskets` | Get baskets |
| POST | `/api/baskets/{name}` | Create new basket |
| GET | `/api/baskets/{name}` | Get basket settings |
| PUT | `/api/baskets/{name}` | Update basket settings |
| DELETE | `/api/baskets/{name}` | Delete basket |
| GET | `/api/baskets/{name}/requests` | Get collected requests |
| DELETE | `/api/baskets/{name}/requests` | Delete all requests |
| GET | `/api/baskets/{name}/responses/{method}` | Get response settings |

## Key resources

- **service** — Service information
- **baskets** — Manage baskets
- **responses** — Configure basket responses
- **requests** — Manage collected requests

## 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:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/rbaskets.in/rbaskets/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 Request Baskets API by hand means passing its Authorization token header, distinguishing the basket token from the service token, and managing basket creation, requests, and responses yourself. Through Jentic you install once, import the Request Baskets API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Request Baskets API puts the basket name in the URL path (`/api/baskets/{name}/...`), so a rule can pin your agent to one basket. You choose the operations it may call, so a destructive one like deleting the basket or clearing its requests is not included unless you add it, keeping the agent to reading captured requests.
- **Credential handling:** Your Request Baskets API 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 'list baskets' or 'read a basket's captured requests', and Jentic returns the matching Request Baskets 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 Request Baskets API use?

The Request Baskets API uses an API key passed 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 get baskets with the Request Baskets API?

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

### What are the rate limits for the Request Baskets 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 baskets through Jentic?

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

### How many endpoints does the Request Baskets API have?

The Request Baskets API exposes 20 endpoints covering service, baskets, responses operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Request Baskets API operations and credentials the agent may use. Since the basket name sits in the URL path (`/api/baskets/{name}/...`), a rule can pin the agent to a single basket, and you choose the exact operations it can call. That means you can allow it to read captured requests with GET `/api/baskets/{name}/requests` while leaving out destructive calls like DELETE `/api/baskets/{name}` or clearing collected requests unless you add them.