canonical: https://jentic.com/apis/swaggerhub.rapp-app-dev-la/aimmune-api

# Rapp App Dev La Aimmune API

This is a sample API for Aimmune for Trial Card form. The API exposes 1 endpoints.

## For AI agents

Programmatically for trial card. Covers 1 operations.

## Scope

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

## Capabilities

- for Trial Card
- Manage developer tools data programmatically
- Integrate Aimmune API into automated workflows
- Query and filter Aimmune API records by parameters
- Monitor Aimmune API operational status and events

## Use cases

### Developer Tools Operations

Use the Aimmune API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including for trial card.

Example prompt: Call POST /trialcard to for trial card

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

AI agents discover and call Aimmune 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 'for trial card', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/trialcard` | for Trial Card |

## Key resources

- **trialcard** — Operations related to trialcard

## Why Jentic

- **Setup:** Wiring the Aimmune API trial card endpoint by hand means pointing at its palforzia.com host, coding the trial-card call, and handling retries yourself even though it takes no credential. Through Jentic you install once, import the Aimmune API from the API Directory, and your agent calls it.
- **Permission scoping:** This API carries its data in the request body of a single trial-card operation, not in the URL path, so you limit the agent to that operation and leave out anything else. Every operation the agent can call is one you chose to allow.
- **Credential handling:** The Aimmune API needs no credential, so there is nothing to store, and any host configuration is held by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'submit a trial card request', and Jentic returns the matching Aimmune 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 Aimmune API use?

The Aimmune 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 for trial card with the Aimmune API?

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

### What are the rate limits for the Aimmune 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 for trial card through Jentic?

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

### How many endpoints does the Aimmune API have?

The Aimmune API exposes 1 endpoints covering trialcard operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and the Aimmune API exposes just one: POST /trialcard for submitting a trial card request. You can allow the agent that single operation and leave every other action out, so it can never reach beyond trial card submission. Any host configuration stays on your own Jentic One instance and is applied only at execution time.