Always current
Nothing to regenerate or redeploy
Endpoints come from your data model as it is now, so a field added in the dashboard is in the next response.
Every entity you create gets a REST API straight away, with filtering, sorting and pagination built in.
Make each entity public or private. Row-level security decides what each caller sees, every project is rate-limited, and your OpenAPI docs write themselves.
Every task works three ways, and all of them change the same project. Here's one: make a products entity public, with only the name and price exposed.
The Anythink dashboard
Choose what's public entity by entity, field by field.
The Anythink CLI
List the endpoints, then call one with your project's credentials.
$ anythink entities update products --public true$ anythink fields update products name --searchable --public$ anythink fields update products price --searchable --public$ anythink api$ anythink fetch "/entities/products/items?page=1&pageSize=20"Claude, through MCP
Ask in plain text. It runs the same commands and shows you what it exposed.
you › “Make the products entity public with only name and price exposed, list the endpoints it now has, and show me the first page of products.”
Always current
Endpoints come from your data model as it is now, so a field added in the dashboard is in the next response.
Access
Each call is checked against the caller's role, and row-level security filters the records it returns, including group-scoped reads for teams.
Search
Fields you mark searchable are indexed as records change, and authenticated search applies the same row-level security as the entity API.
Automation
Creating, updating or deleting a record through the API can trigger a workflow that sends email or push, calls another API or runs a script.
Every entity gets the same REST surface, with permissions, row-level security and rate limiting applied to every call.
List, get, create, bulk create, update, delete and bulk delete for every entity you create. No controller code and no publish step.
Filter on any field with one query parameter per field and operators such as GTE:, LT:, IN: and C: for contains. Sort by any field and page through up to 1,000 records per request.
Expose an entity's chosen fields on a public, read-only endpoint for your website or app, and keep everything else behind authentication with roles and row-level security.
Every project has a per-minute rate limit, with X-RateLimit headers on each response and a 429 when it's exceeded. Each project also gets an OpenAPI description of its API, and anythink api lists every endpoint.
Each call is checked against the caller's role permissions, and row-level security filters the records it returns. Grant records to users or whole groups.
Create API keys with named permissions for CI, scripts and integrations, and send them in the X-Api-Key header. The CLI checks permission names before it creates a key.
In practice
GET https://api.my.anythink.cloud/org/{org_id}/entities/products/items?page=1&pageSize=20&sortBy=price&sortDirection=asc Authorization: Bearer <access token> { "items": [ { "id": 1, "name": "Starter", "price": 29 }, { "id": 2, "name": "Pro", "price": 99 } ], "page": 1, "page_size": 20, "total_items": 2, "total_pages": 1, "has_next_page": false, "has_previous_page": false, "retrieval_time": 8 }
How it works
Create it in the dashboard, with the CLI or by asking Claude. Its endpoints exist as soon as it's saved.
Send a user's JWT or an API key to /org/{org_id}/entities/{entity}/items. Filter, sort and paginate with query parameters.
Give roles read, create, update and delete permissions per entity, and turn on row-level security so each user only gets their own records.
Mark an entity and some of its fields public to serve them read-only from /public/items, with no credentials in your website's code.
Every response carries X-RateLimit headers for your project's per-minute limit. Back off when you get a 429.
See it working
Create an entity in the dashboard and its REST endpoints are live straight away.
Read the REST API guide →Create an entity. Anythink adds list, get, create, update and delete endpoints for it at https://api.my.anythink.cloud/org/{org_id}/entities/{entity}/items straight away, and new fields appear in responses as soon as you add them. Run anythink api to list every endpoint in your project.
Yes. Each project has an OpenAPI description generated from its current entities, alongside the platform endpoints for auth, files, search and more. Browse it in the Anythink dashboard, or list every route from the terminal with anythink api.
Pass page and pageSize for pagination, sortBy and sortDirection for sorting, and one query parameter per field filter, for example ?status=paid&total=GTE:50. Operators include GT, GTE, LT, LTE, IN, ! for not equal, C for contains, SW for starts with and EW for ends with. pageSize can be up to 1,000.
Yes. Mark the entity public and mark the fields you want to expose as public. GET /entities/{entity}/public/items then returns only those fields, read-only, with no credentials. Everything else stays behind a JWT or an API key.
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.