Install Jentic One Beta

Connect the Docswrite Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Docswrite Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdocswrite.com%2Fdocswrite" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdocswrite.com%2Fdocswrite" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Docswrite Public API.

Publish a Google Doc to a connected WordPress site

Publish Markdown or HTML content to one or more CMS connections

List the organization's CMS connections and published posts

Check the status of a publishing job or a published post

Re-publish a post with updated content

GET STARTED

Start building with Docswrite Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Docswrite Public API for, with concrete tasks.

★ Agent Content Publishing

An AI agent connected through Jentic takes a finished Google Doc or Markdown draft and publishes it to the right WordPress or CMS connection, then checks the job status. The Docswrite API exposes the export, posts, and status operations the agent needs, and Jentic injects the credential at call time.

Publish a Markdown draft to a named CMS connection and poll the post status until it is live

Multi-Site Distribution

Teams publishing to several sites push one piece of content to multiple connections at once. The Docswrite API publishes content to one or more CMS connections and lists the organization's connections so an agent can target the right ones.

List the organization's connections and publish an HTML article to the three connections tagged for distribution

Edit and Re-Publish

After an edit, teams push changes to the already-published post rather than creating a duplicate. The Docswrite API re-publishes a post with the updated content and reports the new status, keeping the live version in sync.

Re-publish an existing post with corrected content and confirm the updated post status

Key Endpoints

11 endpoints — the docswrite api publishes google docs and markdown or html content to wordpress and other cms platforms.

METHOD

PATH

DESCRIPTION

POST

/api/export

Publish a Google Doc to WordPress

POST

/api/posts

Publish a Google Doc to any CMS connection

POST

/api/v1/posts

Publish Markdown or HTML to one or more connections

GET

/api/v1/posts/{id}

Get the status of a publish or post

PATCH

/api/v1/posts/{id}

Re-publish a post with changes

GET

/api/connections

List the organization's connections

GET

/api/posts

List the organization's posts across connections

POST

/api/job/status

Get publishing job status

POST

/api/export

Publish a Google Doc to WordPress

POST

/api/posts

Publish a Google Doc to any CMS connection

POST

/api/v1/posts

Publish Markdown or HTML to one or more connections

GET

/api/v1/posts/{id}

Get the status of a publish or post

PATCH

/api/v1/posts/{id}

Re-publish a post with changes

GET

/api/connections

List the organization's connections

GET

/api/posts

List the organization's posts across connections

POST

/api/job/status

Get publishing job status

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Docswrite by hand means choosing between an organization bearer key and per-site tokens in the `x-access-token` or `x-api-key` header, and polling job status yourself. Through Jentic you install once, import Docswrite from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Docswrite puts the post id in the URL path (/api/v1/posts/{id}) while the target connection travels in the request body, so rules bound which operations your agent may call. Limit the agent to the operations it needs, such as listing connections and publishing posts, so re-publish and move operations are not included unless you add them.

Credential isolation

Your Docswrite credential 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.

Intent-based discovery

Agents search Jentic by intent such as 'publish a Google Doc to WordPress' or 'check a publishing job', and Jentic returns the matching Docswrite operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using Docswrite Public API through Jentic.

What authentication does the Docswrite API use?

The Docswrite API accepts an organization API key as a bearer token, per-site API tokens sent in the `x-access-token` or `x-api-key` header, and an oauth2 flow for connected apps, per its OpenAPI spec. Organization-key responses carry RateLimit headers. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

Can I publish a Google Doc to WordPress with the Docswrite API?

Yes. The API exports a Google Doc to a connected WordPress site, publishes a Google Doc to any CMS connection, and publishes Markdown or HTML to one or more connections. You can then check the publishing job status and the status of each post.

Is there a Docswrite MCP server?

You don't need an MCP server to give your agent the Docswrite API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the export and posts operations. Operations load on demand, so your agent's context stays lean instead of holding another server's tool definitions.

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

Yes. Write a rule that allows only the list-connections and publish operations, so the agent can see your CMS connections and publish content but cannot re-publish or move existing posts. Every call the agent makes is logged.

What are the rate limits for the Docswrite API?

Organization-key responses carry RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers, per the Docswrite spec, but it does not publish fixed numbers. Check the Docswrite documentation at https://docswrite.com for current limits before running a large publishing batch.

How do I publish content with the Docswrite API through Jentic?

Search Jentic for an intent like 'publish a Google Doc to WordPress', add the Docswrite API from the directory, and store your credential once. Your agent then calls the publish operation for the connection you choose and polls the post status. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Docswrite Public API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent ManagementapiKey, bearer, oauth211 EndpointsREST

For Agents

Publish Google Docs and Markdown or HTML to WordPress and other CMS connections with Docswrite, list connections and posts, and check publishing job status.

Use for: Publish a Google Doc to my WordPress site, I need to push Markdown content to several CMS connections, List the CMS connections for my organization, Check the status of a publishing job

Not supported: Does not handle website hosting, SEO analysis, or design and theming. Use for publishing documents and content to WordPress and other CMS platforms only.

The Docswrite API publishes Google Docs and Markdown or HTML content to WordPress and other CMS platforms. It exports a Google Doc to a connected site, publishes content to one or more CMS connections, and lists an organization's connections and posts. Job and post status operations report publishing progress, and a re-publish operation pushes edits to an existing post.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

35%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

48%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

53%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Docswrite Public API to your agent

Capabilities

Start building with Docswrite Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Docswrite Public API

Jentic AI Readiness Score

Docswrite Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness