canonical: https://jentic.com/apis/swaggerhub.jnadrowski/agile-documents-api

# Jnadrowski Agile Documents API

Provides PUBLIC API functionality for Agile Documents REST API. The API exposes 2 endpoints.

## For AI agents

Programmatically gets information about a specified task, queues a build of an agile document. Covers 2 operations.

## Scope

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

## Capabilities

- gets information about a specified task
- queues a build of an Agile Document
- Integrate Agile Documents API into automated workflows
- Query and filter Agile Documents API records by parameters
- Monitor Agile Documents API operational status and events

## Use cases

### Developer Tools Operations

Use the Agile Documents API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including gets information about a specified task, queues a build of an agile document.

Example prompt: Call GET /GetTaskStatus to gets information about a specified task

### Data Retrieval and Monitoring

Query Agile Documents API 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 Agile Documents API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Agile Documents 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 'gets information about a specified task', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/GetTaskStatus` | gets information about a specified task |
| POST | `/BuildWithURI` | queues a build of an Agile Document |

## Key resources

- **admins** — Secured admin-only calls
- **developers** — Operations available to regular developers

## Why Jentic

- **Setup:** Wiring the Agile Documents API by hand means pointing at the blueclarity.com host and writing your own request and retry handling around the build and task-status calls. Through Jentic you install once, import Agile Documents from the API Directory, and your agent calls it with no auth to configure.
- **Permission scoping:** This API exposes a build call and a task-status read, so you limit the agent to the operations it needs, such as queuing a document build or checking task status. You choose the operations it may call, and it can do nothing beyond the ones you allow.
- **Credential handling:** The Agile Documents API requires no credential, and any credential you later add 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 'build an Agile Document' or 'get task status', and Jentic returns the matching Agile Documents 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 Agile Documents API use?

The Agile Documents 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 gets information about a specified task with the Agile Documents API?

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

### What are the rate limits for the Agile Documents 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 gets information about a specified task through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets information about a specified task'. Jentic returns the matching Agile Documents API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Agile Documents API have?

The Agile Documents API exposes 2 endpoints covering admins, developers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Agile Documents operations and credentials the agent can use. This API exposes just a build call (POST /BuildWithURI) and a task-status read (GET /GetTaskStatus), so you can allow only what a given agent needs, such as checking task status while blocking document builds. The agent can call nothing beyond the operations you grant.