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

Yes. Write a rule that allows only the operations the agent needs, such as searching graphs and launching research deep-dives, and leave schedule deletion and account changes out. Every call the agent makes is logged, so you can see exactly which research and lookups it ran.

What authentication does the Fodda Context & Research API use?

The Fodda API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec. A number of endpoints are public and need no credential, while metered payment operations accept a Stripe Shared Payment Token presented as a bearer token. 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 get cited evidence with the Fodda API?

Yes. Research and intelligence results carry evidence, and dedicated operations return the evidence and the underlying source chunks for a graph or query. An agent can fetch those chunks to show exactly which source backs each figure before it reports an answer.

What are the rate limits for the Fodda Context & Research API?

The OpenAPI spec does not state request rate limits for the Fodda API. For current limits and fair-use guidance, check the provider documentation at https://www.fodda.ai.

How do I run a research deep-dive through Jentic?

Import the Fodda Context & Research API from the Jentic API Directory, then have your agent issue a request such as 'research this company in depth'. Jentic matches the intent to the deep-dive 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.