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

Yes. Write a rule that allows reading scores, factor breakdowns, and gas regimes but not the portfolio and basket-scoring calls, so the agent can look up vault research without constructing allocations, and every call it makes is logged. The whole API is read-only, so no rule can make it move funds.

What authentication does the AtlasYield API use?

Every endpoint in the AtlasYield spec is public and keyless. An optional partner key sent in the x-api-key header moves you to a higher rate bucket and unlocks partner-only endpoints, per its OpenAPI spec. Through Jentic the partner key, if you use one, 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 score a basket of vaults with the AtlasYield API?

Yes. The basket-scoring endpoint takes a set of vaults and returns their combined Atlas scores, and the portfolio endpoint turns the index into a risk-adjusted allocation, so an agent can evaluate a custom mix rather than one vault at a time. Each vault also exposes its full 16-factor breakdown.

What are the rate limits for the AtlasYield API?

Public endpoints are limited to 60 requests per minute per IP according to the API's own description; an optional partner key raises that to 100 requests per minute in its own bucket. For current limits and partner access, see the AtlasYield documentation at https://docs.atlasyield.club.

How do I read DeFi vault scores with the AtlasYield API through Jentic?

Import the AtlasYield API from the Jentic API Directory, then have your agent issue a request such as 'read the latest vault scores and show the safest ones'. Jentic matches the intent to the scores and factor-breakdown operations and returns their input schemas so the agent builds the right calls. To run it on your own infrastructure, install Jentic One from its GitHub repo.