What authentication does the CRUSH API use?

The API uses HTTP bearer authentication with a JWT. Through Jentic the JWT is stored encrypted in the vault and never enters the agent prompt - Jentic injects it into the Authorization header at execution time.

Can I create a note in CRUSH through the API?

Yes. POST /api/aws/notes with the note body creates a new note in the authenticated user's workspace. Alternatively, POST /api/zapier/create accepts a Zapier-shaped payload for the same outcome through a Zap.

How do I subscribe a Zapier webhook to CRUSH events?

POST /api/zapier/subscribe with the target URL registers the subscription. Use POST /api/zapier/trigger to push events and DELETE /api/zapier/subscribe to unregister when the Zap is removed.

What are the rate limits for the CRUSH API?

The OpenAPI specification does not document specific rate limits. Watch for HTTP 429 responses and contact CRUSH support for production quotas before bulk-importing notes.

How do I capture a note in CRUSH through Jentic?

Run pip install jentic, search 'capture a note in my second brain', load the create-note operation, and execute it with the note text. Jentic injects the JWT bearer automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which CRUSH operations and credentials the agent may use. You can allow only the calls the agent needs, such as creating a note with POST /api/aws/notes or listing note flags with GET /api/aws/noteflags, while withholding the Zapier subscribe, trigger, and create endpoints. Destructive actions like unsubscribing a Zapier webhook with DELETE /api/zapier/subscribe stay off unless you explicitly grant them.