For AI agents

Craftian — for AI agents

Craftian is a cloud you deploy an app to: it arrives with a database, sign-in, permissions, file storage, scheduled jobs and a live URL, none of which you set up. You can create a project, push to it and get a working URL with zero onboarding: no account, no key, no dashboard.

Start here

One file tells you everything: the skill file. It is the single source of truth for agents, and every other resource on this page just points back at it. Fetch it, follow it, or drop it straight into a project as agent instructions.

/craftian-skill.md The skill file. Both modes, the git flow, the data model, the limits and the gotchas. Read this one. /llms.txt The short version in plain text, with one worked example. /.well-known/agent.json The same capability as a small JSON manifest, for discovery. /api API root, a short discovery page linking back to these resources.

The shortest path, in full

Enough to see it work before you fetch anything else. One unauthenticated POST creates a project and returns a clone URL carrying a secret token, which is the credential. The project id is public and is not one:

curl -X POST https://craftian.ai/git/new \
     -H 'content-type: application/json' -d '{"name":"Todo App"}'
# {"appId":"todo-app-a3f9c1","token":"TOK...",
#  "cloneUrl":"https://x:TOK...@craftian.ai/git/todo-app-a3f9c1.git",
#  "liveUrl":"https://todo-app-a3f9c1.craftian.app", ...}

git clone <cloneUrl from the response> todo
cd todo && mkdir -p website && echo "hello" > website/index.html
git add -A && git commit -m "init" && git push origin master

# a push stores files; this is what serves them, at that same liveUrl
curl -X POST -u "x:<token>" -b "SESSION_ID=<session>" \
     https://craftian.ai/git/todo-app-a3f9c1/publish
  • Creating, cloning and pushing need no account. Publishing, and claiming (which is what stops the project expiring), each need a Craftian account and the creation token.
  • An unclaimed project expires 24 hours after it was created, and git operations do not extend that.
  • The project id, the git remote and the live URL never change, so nothing has to be repointed later.
  • Everything else, including owned apps, the data model you push as craftian.ts, the limits and what publishing does and does not build, is in the skill file.