Two endpoints and a bearer token. That's the whole integration.
Create an account and add your first project, pointed at the domain you want to rank.
Add the keywords you want to target, or let AutoScribe suggest some from your site.
Kick off a bulk run and let the pipeline work through it.
Review the drafts, edit anything that needs it, and publish.
Fetch the published posts over the API and render them on your own frontend.
Every request carries your project API key as a bearer token.
Authorization: Bearer YOUR_API_KEY
/api/projects/:project_id/posts
Returns every published post for the project, newest first.
/api/projects/:project_id/posts/:id
Returns one post, including the full markdown body.
The single-post endpoint returns a structured_data array of ready-made JSON-LD. Render each entry inside a <script type="application/ld+json"> tag in your page head — that's the whole integration. It's left out of the list endpoint to keep those payloads small.
You always get an Article. You also get an FAQPage when the article has section headings that ask a question — each one becomes a Question, and the prose beneath it becomes the answer. Answer engines chunk on exactly that structure, so this is the part that decides whether your page gets quoted or skipped.
AutoScribe doesn't know where you render posts, so URLs are omitted by default. Pass base_path and it builds them from your project's base URL: