Can I [user][data sources][authorizers] with the ROOK?

Yes. Use the GET /api/v1/client_uuid/{client_uuid}/user_id/{user_id}/data_sources/authorizers endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ROOK?

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 [user][data sources][authorizers] through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '[user][data sources][authorizers]'. Jentic returns the matching ROOK operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the ROOK have?

The ROOK exposes 20 endpoints covering health, user, physicalhealthsummary operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ROOK operations and credentials your agent may use. ROOK carries the client and user ids in the URL path, so you can pin an agent to a single user's health data, and you choose exactly which operations it may call. That means read operations like getting a physical health summary or listing a user's authorized data sources can be allowed while a state-changing call such as revoking a data-source authorization stays off unless you add it.