canonical: https://jentic.com/apis/go-vip.net/go-vip # Go Vip Patrika AI Generated Articles API The Patrika AI Generated Articles API ingests batches of AI-written articles into a WordPress site in a single authenticated request. Each request carries up to five articles and accepts text-only content or content with Base64-encoded images, with the featured image supplied as a Base64 payload. Image URLs inside the post body are not accepted, so the endpoint takes self-contained article payloads your agent assembles before posting. ## For AI agents Ingest up to five AI-generated articles per request into a WordPress site, with text-only content or Base64-encoded images and a Base64 featured image. ## Scope Does not edit, schedule, or delete existing posts, and does not manage media libraries. Use for ingesting batches of AI-generated articles into the site only. ## Capabilities - Ingest up to five AI-generated articles in a single request - Publish text-only articles or articles with Base64-encoded images - Set each article's featured image as a Base64 payload - Submit the batch with a bearer token to the article ingestion endpoint ## Use cases ### Agent-Driven Article Ingestion An AI agent writes articles and needs to get them onto a WordPress site without a human pasting each one in. It assembles the article payload, encodes any images as Base64, and posts the batch to the ingestion endpoint with a bearer token. Jentic exposes the operation with its input schema so the agent builds a valid article object, including the Base64 featured image, on the first call. Example prompt: Assemble a text article with a Base64 featured image and post it to the article ingestion endpoint, then confirm the response accepted it ### Bulk AI Content Publishing A content pipeline generates several articles at once and submits them together to reduce round trips. The Patrika API accepts up to five articles in one request, so the pipeline groups a batch and posts it in a single call. Text-only articles are allowed, so drafts without imagery still publish. Example prompt: Group five generated articles into one request and submit the batch to the ingestion endpoint ### Image-Rich Article Submission An editorial workflow publishes articles that include images alongside the text. The Patrika API takes images as Base64, with the featured image supplied the same way, because image URLs inside the post body are not accepted. The workflow encodes each image before posting so the article arrives complete. Example prompt: Encode a featured image as Base64, attach it to an article payload, and submit the article to the ingestion endpoint ## Key resources - **Articles** — Ingest up to five AI-generated articles per request, with text-only content or Base64 images ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 79 / 100 - AI-Readiness & Agent Experience: 35 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/go-vip.net/go-vip/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Patrika API by hand means managing its bearer token and building article payloads that follow its rules: up to five articles per request, Base64 images only, and no image URLs inside the body. Through Jentic you install once, import Patrika from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Patrika exposes a single article-ingestion operation that carries the articles in the request body, so a rule bounds your agent to exactly that operation. There is nothing else in the surface to expose, and every call your agent makes is logged. - **Credential handling:** Your Patrika token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'ingest AI-generated articles', and Jentic returns the Patrika ingestion operation with its input schema so the agent builds a valid article batch without reading the reference docs. ## Related APIs - **Contentful** — Contentful is a headless CMS with full content modeling and delivery. - **Blogger** — Blogger publishes and manages posts on Google's blogging platform. - **ContentStudio** — ContentStudio handles content discovery and social distribution. ## FAQ ### What authentication does the Patrika API use? The Patrika API authenticates with a bearer token in the Authorization header per its OpenAPI spec. Through Jentic that token is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in your agent's prompt or logs. ### Can I publish multiple articles at once with the Patrika API? Yes. A single request can carry up to five articles, so your agent batches generated content and posts it in one call. Text-only articles are accepted, and images travel as Base64 rather than URLs. ### What are the rate limits for the Patrika API? The Patrika spec states a rate limit of one request every ten seconds. Space batch submissions to that limit, and because each request carries up to five articles, batching reduces how often your agent needs to call. ### Is there a Patrika MCP server? You do not need an MCP server to give your agent the Patrika API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the ingestion operation. The operation is discovered on demand, so your agent's context stays lean instead of loading a full tool list up front. ### Can I limit what my agent is allowed to do with the Patrika API? Yes. Because the Patrika API has a single ingestion operation, a rule that allows it lets the agent submit article batches and nothing more, and every call it makes is logged. There are no update or delete operations in the surface to withhold. ### How do I ingest articles with the Patrika API through Jentic? Search Jentic for 'ingest AI-generated articles', and it returns the Patrika ingestion operation with its input schema. Your agent builds the article payload with any Base64 images and posts the batch. To run it on your own infrastructure, install Jentic One from its GitHub repo.