Can I start and stream a research task with the Autumn Task API?

Yes. POST /task starts a durable task and POST /task/stream starts one and streams its events as server-sent events. You can then read status with GET /task/{task_id} and the result with GET /task/{task_id}/output, or continue the task with more input.

What are the rate limits for the Autumn Task API?

Autumn meters work against a credit balance that GET /credits reports rather than a fixed request ceiling, and the OpenAPI spec does not state request limits. Read your credits before a batch, watch for HTTP 429 responses, and check Autumn's documentation for the current limits.

How do I start a research task with the Autumn Task API through Jentic?

Search Jentic for 'start a research task', and it returns the Autumn operation with its input schema. Load the schema and execute POST /task with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an Autumn Task API MCP server?

You don't need an MCP server to give your agent the Autumn Task API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the task operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

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

Yes. Autumn puts the task id in the URL path, so a rule can allow only starting tasks and the read operations that track them, while continue, re-execute, and stop stay off the table until you add them. Every call runs through your own instance where it is logged for review.