Build and check apps
with your AI assistant.

For an authorized API workflow.

Use a team-scoped API key with the required permissions. This example queues real build work if you run it with valid access; it can consume credits. Keep the key out of shared prompts and source files.

curl -X POST https://www.overskill.com/api/v1/generation_queue \
  -H "User-Agent: OverSkill/206fd15 (+https://overskill.com)" \
  -H "X-API-Key: os_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"Build a coffee shop landing page with hours and a menu"}'

{
  "job_id": "example_job_id",
  "app_id": "example_app_id",
  "message_id": 456,
  "status": "queued",
  "status_url": "https://www.overskill.com/api/v1/generation_queue/example_job_id",
  "app_url": "https://www.overskill.com/account/apps/example_app_id/edit"
}

Identifiers vary. This shortened response is illustrative, not an observed build. Completion time varies; the API’s estimate is not a measured result for your app.

Poll status_url with the same authorized credential about every 15 seconds. On completed, inspect app.preview_url. Stop on failed or cancelled and inspect the result before retrying. Build completion is not publication or browser acceptance.

Manage keys in Team Settings → API Keys. API documentation describes permissions and response fields; MCP setup uses OAuth instead.

Skill files are instructions.

Read SKILL.md or follow your host’s setup instructions. A downloaded skill does not grant account access or connect a tool.

What works without an API key.

Public documentation and discovery can be read without a key. The email sign-in endpoint starts authentication; it does not grant builder access. Builds require an authorized account and credits.

Find the documented interfaces.

Discovery files describe interfaces and authentication. A published declaration does not establish successful execution or grant permission to act.

Connection support and declared roadmaps.

Commerce discovery documents describe existing hosted checkout surfaces. Native agent payment and transaction protocols remain planned; publishing metadata does not implement those transactions.