Shvydko for AI agents

Give your agent the current contract, validate the request locally, and connect typed decisions to your server code.

Documentation your agent can read

llms.txt contains an index of topics and links to Markdown. llms-full.txt contains the full text of those same pages. OpenAPI describes only the public GET /v1/models and POST /v1/systemone endpoints that use an API key. These files are accessible without signing in; model requests require a key.

Mode, rates, and quotas may change. Read /api/config and get model context through GET /v1/models. A published rate does not mean paid mode is enabled: requests cost zero in preview.

Agent index Full documentation text OpenAPI 3.1 JSON

A task for your coding agent

Copy this task into your agent's workspace

Connect Shvydko to my server application.

1. Read https://shvydko.ai/en/llms.txt and https://shvydko.ai/openapi.json.
2. Use the /v1/systemone HTTP API. Do not install an invented SDK
   or use chat/completions.
3. Read SHVYDKO_API_KEY only from the server environment.
   Do not expose it in code, logs, URLs, the browser, or messages.
4. Prepare a request: state contains task facts; questions contains Choice, Score,
   or Noul with clear criteria and a manual route for uncertainty.
5. Check the HTTP status, response structure, request_id, and usage.
   Handle 401, 402, 403, 409, 413, 422, 429, 502, and 503.
   Do not retry POST automatically after a network timeout.
6. Add local checks for a valid response, an error,
   and an unknown category. The model only proposes a decision; my application
   performs the external action after its own validation.
7. Show the payload without secrets before making a real call.
   At my request, make one controlled call and check usage.

This is an instruction for your coding agent, not a separate MCP server or published SDK. Access to the documentation does not grant access to your account.

Turn the decision into a tool

In your agent's tool registry, create a server function named evaluate_decision with state and questions parameters matching the DecisionRequest schema in OpenAPI. You can omit the model name: the service will select the current public model.

The function should return validated answers, request_id, and usage. Do not let a model response choose an HTTP request destination, payment recipient, or other external action on its own. If one step depends on the previous one, validate the first response before building the next request in code.

Server function using fetch Python HTTP client Decision with a manual route

What to check before launch

The request shape matches OpenAPI, the question has a stable ID, and the criteria cover your allowed outcomes.
An invalid key, request limit or service outage must not trigger an external action.
A mock response tests only your code; assess decision quality on your own labeled examples.
After an authorized real run, request_id, tokens and cost_usd agree with Usage in the console.