App de Bock / 01.1 · AI & vibe-code friendly

Built for the tools writing your code.

Pretty docs don’t help when Claude is the one reading them. So the AI-friendliness lives in the protocol, not the README.

Made for
AI Coding Tools
Schema
llms.txt + OpenAPI 3.1
Agents
MCP server Soon
Auth
One header

01 · Schema

One fetch, whole schema.

Every API ships a native llms.txt and an OpenAPI 3.1 spec. Point your assistant at it and it knows the entire API in a single request.

No scraping docs pages. No hallucinated endpoints. No “please paste the docs again”.

GET /llms.txtOK

$ curl https://appdebock.nl/llms.txt

# App de Bock
> Small, fast endpoints. One header. JSON in, JSON out.

## APIs
- [[Name] v1](https://api.[name].nl/llms.txt): [what it does]
- [[Name] v1](https://api.[name].nl/llms.txt): [what it does]

Coming soon

02 · Errors

Errors that fix themselves.

When a call fails you get a deterministic payload: what broke, what was received, what was expected and how to fix it.

Your LLM reads it and patches the call before you’ve even looked up. Fewer loops, fewer tokens, fewer “it still doesn’t work”.

422 · invalid_parameterOK

{
  "error": "invalid_parameter",
  "field": "currency",
  "received": "USD",
  "expected": ["usd", "eur", "gbp"],
  "fix_suggestion": "Convert currency string to lowercase."
}

> agent reads fix_suggestion · retries
200 OK  1 retry, 0 humans

Coming soon

03 · Agents

Plugs straight into your editor.

Each API comes with an MCP server, so agents in Cursor or Claude Desktop can call it natively.

No glue code, no wrapper library. Add the config, restart your editor, ask for what you need.

mcp.jsonOK

{
  "mcpServers": {
    "appdebock": {
      "command": "npx",
      "args": ["-y", "[mcp-package]"],
      "env": { "API_KEY": "your-key" }
    }
  }
}

04 · Auth

One key. One header. Done.

Complex OAuth flows and stateful multi-header sign-offs break AI code generation constantly.

So auth is one bearer token, simple enough for your assistant to get right on the first try, even running locally at 2am.

The usual

  1. Register an app
  2. Set a redirect URI
  3. Exchange a code for a token
  4. Refresh the token
  5. Send three headers
  6. Hope the AI remembers all of it

Here

  1. -H "Authorization: Bearer $API_KEY"

// That’s it. That’s the list.

Try it

Paste this into your assistant.

See the APIs Read the docs

Prompt

Read https://appdebock.nl/llms.txt and build me a [thing] that uses the [API name] endpoint. My key is in $API_KEY.