Public API
Your website reads content without a key
Mark a content type and its fields public, and /entities/articles/public/items serves them without sign-in, with paging, sorting and field filters. Fields you don't mark public stay private.
Anythink works as a headless CMS: model content types, edit them in the Anythink dashboard, and serve them to your website through a public REST API.
Create an articles content type your website can read.
The Anythink dashboard
Model the content type, then your editors write in the same place.
The Anythink CLI
The same content type, scriptable and repeatable.
$ anythink entities create articles --public$ anythink fields add articles title --type varchar \--required --public --searchable$ anythink fields add articles body --type text \--display rich-text --public$ anythink fields add articles hero_image --type file \--display file --public$ anythink fields add articles status --type varchar \--display select --options draft,in_review,published --publicClaude, through MCP
Describe the content type. The assistant runs the same commands.
you › “Create an articles content type for our blog with a required, searchable title, a rich-text body, a hero image and a status of draft, in review or published. Make it publicly readable so our website can fetch published articles.”
Content types are entities, so every part of Anythink works with them.
Public API
Mark a content type and its fields public, and /entities/articles/public/items serves them without sign-in, with paging, sorting and field filters. Fields you don't mark public stay private.
Media
A worker probes each upload with ffprobe and writes duration, dimensions, bitrate, size and a hash back to the file record. Your site can show a running time without reading the file itself.
Editorial
The kanban view groups any content type by a status field. Moving a card updates the record, so the board and the API never disagree about what's published.
Automation
Trigger a workflow when an article's status changes to published: post to Slack, email your subscribers or call a webhook to rebuild your site.
Content types are ordinary Anythink entities, so the same project holds your content, your users and your app data.
Give a text field the rich-text display and editors write long-form copy in the dashboard. The body sits on the same record as its title, author, category and hero image, so your site can query on any of them.
Uploads stream straight to object storage. Anythink then probes each image, audio or video file out of process and records its size, dimensions, duration and a SHA-256 hash. Downloads use short-lived signed URLs, and files marked public need no sign-in.
Create an entity for each content type and give it the fields it needs: text, rich text, dates, selects, relationships, files and JSON. Each type gets a REST API as soon as it's saved.
Switch any content type to the kanban view and it groups records by a status field you choose. Editors drag an article from in review to published; grid and calendar views read the same records.
Mark fields as searchable and Anythink indexes them, with filters, facets, sorting and highlighting. Public search only ever returns fields you've marked public.
Create an editor role that can read, create and update articles but not delete them. Add row-level security when writers should only see their own drafts.
In practice
GET https://api.my.anythink.cloud/org/{org_id}/entities/articles/public/items?status=published&sortBy=id&sortDirection=desc&page=1&pageSize=10
How it works
Create an entity for articles, case studies or products and add the fields each one needs, including rich text, files and relationships to authors or categories.
Create an editor role with read, create and update permissions on your content types, then invite your writers to the Anythink dashboard.
Editors write in the dashboard and move content through draft, in review and published on the kanban view.
Your website calls the public endpoint for each content type and asks for published records only. A field you add in the dashboard appears in the response straight away.
Editorial board
Switch the articles entity to Kanban View and drag cards between statuses.
Flexible data views →Yes. You model content types as entities, editors manage them in the Anythink dashboard, and your website or app reads them through a REST API. Public content types can be read without an API key.
Because it's also a full backend, the same project can hold sign-in, subscriptions and workflows for the product the content supports.
No. There's no built-in draft copy of a record and no revision history to roll back to. Most teams use a status field (draft, in review, published) and have the website request only published records.
If you need full revision history or scheduled preview environments, a dedicated CMS is the better fit today.
No. Anythink stores, secures and serves structured content, and your front end (Next.js, a mobile app, a static site generator) decides how it looks. There's no drag-and-drop page layout editor.
For API-first content, yes: custom content types, a REST API, roles, files and search. Anythink adds native subscriptions, push notifications and a visual workflow engine in the same project.
It's fully managed, so there are no servers to run or upgrade, and Enterprise customers can have a dedicated stack.
Still have questions?
Get in TouchEvery feature reads from the same data model, so each one you add works with the rest.
The dashboard, the CLI, MCP and the SDK, plus guides for moving from other platforms.
How founders, agencies and enterprise teams use Anythink.
Guides and reference at docs.anythink.cloud.
All the tools you need to start small and create something big