Can I issue session token with the Quiltt API?

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

What are the rate limits for the Quiltt 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 issue session token through Jentic?

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

How many endpoints does the Quiltt API have?

The Quiltt API exposes 17 endpoints covering accounts, authentication, connections operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Quiltt operations and credentials the agent may use, and it can call nothing else. Since Quiltt puts the profile id in the URL path (/v1/profiles/{id}), you can pin the agent to a single profile so it reads that profile and nothing more. You choose which operations to expose, so destructive calls such as revoking a session with DELETE /v1/users/session stay off limits unless you add them.