vee.kr

Developers

Automate Bidama

Use REST with scoped API keys or connect agents to the OAuth remote MCP server. Both share the same ownership, quotas, rate limits, and audit trail.

Start in three steps

  1. For REST, sign in and create an API key under API keys. Copy the plaintext once — it is shown only at creation.
  2. Choose scopes: read for listing and analytics, write for create/update, delete for soft-delete.
  3. Call REST at /api/v1/* or connect ChatGPT, Claude, or another remote MCP client to /mcp with OAuth.

Pick a surface

REST API Full REST endpoint catalog, request shapes, scopes, errors, and the OpenAPI download. MCP MCP OAuth remote MCP setup and the full tool catalog: every operation and type branch for agents.

What stays the same

  • Every call is scoped to your account. Another owner's slug returns not found.
  • Errors use a stable error_code envelope. Rate limits return 429 with Retry-After.
  • Edits can use ETags: read a resource, then send If-Match / if_match on change.