Install Jentic One Beta

Connect the Request Baskets API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Request Baskets 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%2Frbaskets.in%2Frbaskets" | 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%2Frbaskets.in%2Frbaskets" | 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 Request Baskets API.

Get baskets

Create new basket

Update basket settings

Delete basket

Access Request Baskets API developer tools resources via REST API

GET STARTED

Start building with Request Baskets API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

20 endpoints — restful api of [request baskets](https://rbaskets.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Request Baskets API through Jentic.

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.

Rbaskets In Request Baskets API

Name: Request Baskets API
Brand: Request Baskets API
Availability: InStock

AI ReadinessFoundational (C+)60/100

See full scorecard

Developer ToolsMonitoring ObservabilityapiKey20 EndpointsREST

For Agents

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

Use for: I need to baskets, I want to new basket, Search for basket settings, Find all basket settings

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

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.

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.

100%

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

26%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

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

100%

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: FSignals: 4

76%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

67%

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.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Request Baskets API to your agent

Capabilities

Start building with Request Baskets API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rbaskets In Request Baskets API

Jentic AI Readiness Score

Request Baskets 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