canonical: https://jentic.com/apis/agilitywriter.ai/agilitywriter # Agility Writer API Jentic publishes the only available OpenAPI specification for Agility Writer API, keeping it validated and agent-ready. Agility Writer is an AI long-form article generator that produces SEO-optimised content in a job-based flow - a single create call kicks off generation, and a status call returns the article body when ready. The API exposes two endpoints under /api/v1: one to start an article job with a topic and configuration, and one to retrieve the generated article by job ID. Authentication is a Bearer-style token sent in the Authorization header. ## For AI agents Generate long-form, SEO-optimised articles asynchronously: submit a topic to start a job, then poll the status endpoint until the article is ready. ## Scope Does not handle image generation, content publishing, or keyword research - use for AI long-form article drafting only. ## Capabilities - Submit an article generation job with a topic, keywords, and SEO targeting parameters - Poll an article job by ID to retrieve status and the finished article body - Produce SEO-optimised long-form drafts ready for direct publication or review - Drive batch content production by issuing concurrent create calls per topic - Integrate AI article generation into editorial pipelines without managing prompts ## Use cases ### Programmatic Long-Form Content Production Marketing teams and content agencies submit topics in bulk and let Agility Writer generate full drafts in the background. Each topic becomes one POST call, returning a job ID; the agent then polls the GET endpoint until the article body is ready. The asynchronous design suits long generations that may take minutes per article, and a single Authorization header covers all calls. Example prompt: POST / with topic 'sustainable packaging trends 2026' and target keyword, then poll GET /{articleId} until status is complete ### SEO-Targeted Article Drafting Editors brief Agility Writer with a primary keyword, secondary keywords, and target length. The system returns a structured long-form draft optimised for on-page SEO, ready for human review or downstream CMS publishing. Useful for pillar page production where a consistent keyword frame matters more than per-article handcrafting. Example prompt: Submit POST / with primary keyword 'best running shoes for flat feet' and 1500-word target, retrieve the article when ready ### AI Agent Content Pipeline via Jentic An agent can chain Agility Writer with downstream publishing APIs through Jentic - generating an article, waiting for completion, and pushing the result into a CMS. Jentic stores the Authorization token in its vault and injects it at execution time, so the credential never appears in the agent transcript or chain memory. Example prompt: Use Jentic to search 'generate an SEO article', execute the create call, poll for status, then call the CMS publish endpoint ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | / | Create a new article generation job | | GET | /{articleId} | Get article job status and content | ## Key resources - **Articles** — Article generation jobs - create one and poll for status and body ## Why Jentic - **Setup:** Wiring the Agility Writer API by hand means managing its Authorization token and coding the two-step async flow that creates an article and then polls for it. Through Jentic you install once, import the Agility Writer API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Agility Writer puts the article id in the URL path for reads (/{articleId}), while article creation takes its input in the body, so a rule can pin the agent to reading a specific article or limit it to the create operation. You choose which operations are in the allowed set, so anything you leave out is not reachable. - **Credential handling:** Your Agility Writer token is stored once, encrypted, by your own Jentic One instance and attached at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'generate an SEO article', and Jentic returns the create-article and get-article operations with their schemas so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **OpenAI** — General-purpose LLM API for synchronous text generation with full prompt control - **Anthropic Messages** — Claude messages API for synchronous long-form generation with streaming - **Copy.ai** — AI copywriting API with templated marketing content generators - **Ahrefs** — SEO research API providing keyword and backlink data to brief content jobs - **Semrush** — SEO and competitive research API for keyword and topic discovery ## FAQ ### Why is there no official OpenAPI spec for Agility Writer API? Agility Writer does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Agility Writer API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Agility Writer API use? The API uses an apiKey header named Authorization carrying your Agility Writer key. Jentic stores the key in its vault and injects it on each request, so the raw token never enters the agent's context window. ### How long does it take to generate an article through the Agility Writer API? Generation is asynchronous. POST / returns an articleId immediately and the article body becomes available on GET /{articleId} once the job completes. Typical long-form jobs take minutes rather than seconds, so poll on a backoff rather than a tight loop. ### Can I generate multiple articles in parallel? Yes - each POST / starts an independent job and returns its own articleId. There is no batch endpoint, so issue concurrent create calls and track each articleId separately when polling for status. ### How do I generate an article through Jentic? Search Jentic for 'generate an SEO article'. Load the POST / schema, execute with your topic and target keyword, capture the returned articleId, then load and execute GET /{articleId} to retrieve the finished article body. Jentic handles the Authorization header end-to-end. ### What are the rate limits for the Agility Writer API? The OpenAPI spec does not declare explicit rate limits. Because generation is long-running, throughput is naturally bounded by job concurrency rather than request rate. Use exponential backoff on the GET /{articleId} polling call. ### Can I limit what my agent is allowed to do with the Agility Writer API? Yes. Because you run Jentic One yourself, your own rules decide which of the Agility Writer operations your agent can call and which credentials it may use. The API exposes just two operations, creating an article (POST /, with the topic and configuration in the request body) and reading an article by id (GET /{articleId}, with the id in the URL path), so you can allow only creation, restrict the agent to reading a specific article id, or permit both. Any operation you leave out of the allowed set is not reachable by the agent.