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

Yes. Write a rule that allows only the operations the agent needs, such as reading KPIs and running queries, and leave alert deletion and segment changes out. Every call the agent makes is logged, so you can see exactly which reports it ran.

What authentication does the Formo API use?

The Formo API authenticates with a workspace API key presented as a bearer token on api.formo.so per its OpenAPI spec. Event ingestion uses a separate project SDK write key, also a bearer token, and metered endpoints answer a 402 challenge with a payment payload in the X-PAYMENT or Authorization header. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I run a custom query with the Formo API?

Yes. Beyond the prebuilt KPI, funnel, and retention reports, one operation runs a SQL query directly against the analytics data, and saved charts on a board expose their own query endpoint. An agent can read a prebuilt metric or drop to SQL when a question needs it.

What are the rate limits for the Formo API?

The OpenAPI spec does not state request rate limits for the Formo API. For current limits and fair-use guidance, check the provider documentation at https://api.formo.so.

How do I report product metrics through Jentic?

Import the Formo Public API from the Jentic API Directory, then have your agent issue a request such as 'show me the conversion funnel for signups'. Jentic matches the intent to the funnel operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.