canonical: https://jentic.com/apis/awraiter.ai/awraiter

# AwrAIter REST v1

The AwrAIter API drafts, schedules, and analyses social channel content from one endpoint per tool. It turns text into post drafts, builds polls and content plans, finds a free slot in a channel's calendar, and schedules or cancels posts. Read tools return channel insights, statistics, recent posts, and search over a channel's posts and sources, while quality tools score a draft and check it for duplicate content before it goes out. Governance tools set a brand brief, channel header and footer, and an autopilot approval policy so a channel stays on-voice.

## For AI agents

Draft, schedule, and analyse social channel posts: create drafts from text, build polls and content plans, find free slots and schedule posts, score drafts, check for duplicates, and read channel insights and stats.

## Scope

Does not handle ad campaigns, direct messaging, or payment processing. Use for drafting, scheduling, and analysing channel posts only.

## Capabilities

- Create a post draft from text, or build a poll draft for a channel
- Find a free slot in a channel's calendar and schedule or cancel a post
- Build and read a content plan for a channel
- Score a draft and check it for duplicate content before publishing
- Read channel insights, statistics, and recent posts
- Search a channel's posts and sources, and draft from those sources
- Set a brand brief, channel header and footer, and an autopilot approval policy

## Use cases

### Agent Draft-and-Schedule

An AI agent connected through Jentic turns a brief into a scheduled post: it drafts from text, scores the draft and checks it for duplicate content, finds the next free slot in the channel calendar, and schedules it. Each tool is a single endpoint, so the agent chains them without juggling a batch format.

Example prompt: Draft a post from a text brief, score it, check it for duplicates, find the next free slot for the channel, and schedule it

### Channel Performance Review

A social manager pulls a channel's insights, statistics, and recent posts to review how content is performing. The AwrAIter API returns the stats over a period and the recent-post history in structured form, so an agent can summarise reach and cadence without scraping the channel.

Example prompt: Fetch a channel's statistics for the last 30 days and its ten most recent posts, then summarise posting cadence and engagement

### On-Brand Content Governance

A team keeps a channel on-voice by setting a brand brief, header, and footer, then applying an autopilot approval policy that decides which drafts can post automatically. The AwrAIter API also checks each new draft for uniqueness against prior posts, so repeated content is caught before it ships.

Example prompt: Set a channel's brand brief, apply an autopilot approval policy, and check a candidate draft for duplicate content

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/create_post_from_text` | Create a draft from text |
| POST | `/api/v1/schedule_post` | Schedule or publish a post |
| POST | `/api/v1/cancel_scheduled_post` | Cancel a scheduled post |
| GET | `/api/v1/find_free_slot` | Find a free slot in a channel's calendar |
| POST | `/api/v1/create_content_plan` | Create a content plan |
| GET | `/api/v1/get_channel_stats` | Read channel statistics |
| GET | `/api/v1/get_channel_insights` | Read channel insights |
| GET | `/api/v1/list_channels` | List team channels |

## Key resources

- **Drafts and posts** — Create drafts from text, build polls, score and preview posts, schedule and cancel them
- **Content plans** — Create and read a channel's content plan and find free scheduling slots
- **Channels** — List channels and read insights, statistics, memory, and recent posts
- **Sources** — Search sources and channel content, and draft from sources
- **Governance** — Set brand brief, header, footer, autopilot policy, and the ban list

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 93 / 100
  - Security: 60 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/awraiter.ai/awraiter/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the AwrAIter API by hand means managing a bearer token, learning its one-endpoint-per-tool layout, and sending an Idempotency-Key on every write tool so retries are safe. Through Jentic you install once, import the AwrAIter API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** AwrAIter exposes one endpoint per tool and carries the channel id in the query or body, so a rule bounds which tools your agent may call, not which channel. You choose the operations it may call, so the write tools like schedule-post, cancel-scheduled-post, and set-autopilot-policy are not included unless you add them.
- **Credential handling:** Your AwrAIter 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 'schedule a post' or 'read channel statistics', and Jentic returns the matching AwrAIter tool with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpost** — Mixpost is a self-hosted social scheduler, overlapping with AwrAIter's draft-and-schedule tools.
- **Buffer** — Buffer schedules and publishes posts across networks, a comparable publishing surface to AwrAIter.
- **Sprout Social** — Sprout Social adds deeper cross-network analytics and engagement alongside AwrAIter's channel stats.

## FAQ

### What authentication does the AwrAIter API use?

The AwrAIter API authenticates with a bearer token, a personal access token or OAuth token sent as Authorization: Bearer, per its OpenAPI spec. The same token works across the read and write tools. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context.

### Can I draft and schedule a post with the AwrAIter API?

Yes. You create a draft from text, optionally score it and check it for duplicate content, find the next free slot in the channel's calendar, and schedule it. A scheduled post can also be cancelled, so an agent can manage the full draft-to-publish path.

### What are the rate limits for the AwrAIter API?

The OpenAPI spec does not state fixed numeric rate limits for the AwrAIter API; write tools accept an Idempotency-Key header so retries are safe. Check https://awraiter.ai for the current limits that apply to your plan.

### Is there an AwrAIter MCP server?

Yes, AwrAIter exposes an MCP server alongside this REST surface. You can also connect the AwrAIter API directly through Jentic: your agent gets the full 56-endpoint surface without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which tools the agent may call.

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

Yes. Because AwrAIter maps one endpoint to each tool, you write a rule that allows only the read tools, such as channel stats, recent posts, and content search, and leave out the write tools like schedule-post, cancel-scheduled-post, and set-autopilot-policy. The agent can then analyse a channel but never publish, and every call it makes is logged.

### How do I schedule a post through Jentic?

Import the AwrAIter API from the Jentic API Directory, store your access token once, and have your agent search Jentic for 'schedule a post'. Jentic returns the schedule-post operation with its input schema so the agent sends the channel and draft and reads back the scheduled time. To run it on your own infrastructure, install Jentic One from its GitHub repo.