What authentication does the Marrow Agent Governance API use?

The agent operations require a Marrow API key passed as a bearer token per the OpenAPI spec, while the public health and discovery endpoints need no credential. Through Jentic the key is stored encrypted in your own Jentic One instance and supplied only when an authenticated call runs, so it never reaches the agent's context.

Can I evaluate an action before the agent runs it with the Marrow Agent Governance API?

Yes. The runtime evaluate operation takes a proposed action and returns governance guidance before execution, and a separate commit operation closes the action with its outcome and proof afterward. Together they bound what the agent does and leave a verifiable record of it.

What are the rate limits for the Marrow Agent Governance API?

The OpenAPI spec does not specify rate limits. A public status endpoint reports component health you can poll, and you can confirm the request limits for your tenant in the Marrow documentation at https://getmarrow.ai.

Can I limit what my agent is allowed to do with the Marrow Agent Governance API?

Yes. Write a rule that permits only the read operations, reading context and metrics, when the agent should observe governance, and add the permit and commit operations only for workflows that actually govern actions, with every call logged.

How do I evaluate an agent action with the Marrow Agent Governance API through Jentic?

Search Jentic for 'check if an agent action is allowed' to surface the evaluate operation, load its input schema, pass the proposed action, and execute, then commit the outcome once the action runs. To run it on your own infrastructure, install Jentic One from its GitHub repo.