canonical: https://jentic.com/apis/swaggerhub.rjericho/apidoc

# Rjericho APIDOC

AWS Lambda API specs. The API exposes 14 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically access APIDOC resources. Covers 14 operations with apiKey, bearer authentication.

## Scope

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

## Capabilities

- Access APIDOC resources via REST API
- Manage developer tools data programmatically
- Integrate APIDOC into automated workflows
- Query and filter APIDOC records by parameters
- Monitor APIDOC operational status and events

## Use cases

### Developer Tools Operations

The API provides 14 endpoints for developer tools operations.

Example prompt: Execute a primary operation against the APIDOC

### Data Retrieval and Monitoring

Query APIDOC resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary APIDOC endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call APIDOC 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, bearer tokens manually.

Example prompt: Search Jentic for 'apidoc', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **orders** — Orders methods
- **cards** — Cards methods
- **operations** — Operations method
- **bitcoin** — Methods to operate with bitcoin ecosystem

## Why Jentic

- **Setup:** Wiring APIDOC by hand means learning that it accepts either an X-API-Key header or a bearer token, wiring whichever you use, and handling requests and retries yourself. Through Jentic you install once, import APIDOC from the API Directory, store the key or token once, and your agent calls it.
- **Permission scoping:** You choose which APIDOC operations the agent may call, so you can limit it to the operations it needs and leave everything else out of the allowed set. Grant only the reads or writes a task requires, and destructive operations stay unavailable unless you add them.
- **Credential handling:** Your APIDOC key or bearer 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 describing the APIDOC task at hand, and Jentic returns the matching APIDOC 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 APIDOC use?

The APIDOC uses apiKey, bearer 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.

### What are the rate limits for the APIDOC?

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 use apidoc through Jentic?

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

### How many endpoints does the APIDOC have?

The APIDOC exposes 14 endpoints covering orders, cards, operations operations.

### Does the APIDOC support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because you self-host Jentic One, your own rules decide which APIDOC operations and credentials the agent may use. You can allow only the specific reads or writes a task needs, such as querying orders or cards, and leave the rest out of the allowed set. Destructive operations, including those in the bitcoin and operations groups, stay unavailable to the agent unless you explicitly add them.