Can I store secrets in an encrypted vault with the agentic-endpoints API?

Yes. The vault store operation claims a namespace and returns a one-time namespace token, and you then store, retrieve, list, check existence, delete, and rotate tokens for items under that namespace. Items stored as private are kept as ciphertext the service cannot read.

What are the rate limits for the agentic-endpoints API?

The OpenAPI spec does not specify rate limits; pricing is pay-per-call and each paid endpoint answers HTTP 402 with its price. Check the documentation at https://agentic-endpoints.com for current limits and prices.

How do I scrape a web page with the agentic-endpoints API through Jentic?

Search Jentic for 'scrape a web page' and it returns the scrape operation with its input schema. Your agent sends the target URL, is debited at list price from your prepaid credit, and gets the extracted text back. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the agentic-endpoints API?

Yes. Write a rule that allows only the scrape and pdf-parse operations, so the agent can extract text but cannot delete vault items or rotate a namespace token, and every action it takes is logged. Because these operations carry their inputs in the request body, the rule bounds which operations run rather than which item a request names.

Is there an agentic-endpoints MCP server?

You don't need an MCP server to give your agent the agentic-endpoints API. Jentic connects it directly from the API Directory: import it, store your prepaid credit token once, and your agent calls the scrape, parse, compress, vault, and meeting operations on demand without loading another server's tool definitions into its context.