Can I verify authentication with the Rewiser?

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

What are the rate limits for the Rewiser?

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 verify authentication through Jentic?

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

How many endpoints does the Rewiser have?

The Rewiser exposes 4 endpoints covering create_multiple_transactions, get folders, get recent transactions operations.

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

Yes. Because you self-host Jentic One, you decide which Rewiser operations the agent may call, and your own rules govern the stored bearer token at execution time. Since Rewiser uses function-style endpoints whose targets travel in the request body rather than as a resource id you can pin, you scope access at the operation level, granting only what the agent needs such as GET /get-recent-transactions or GET /get-folders. Write operations like POST /create_multiple_transactions stay out of reach unless you explicitly add them.