> For the complete documentation index, see [llms.txt](https://k4k3ru.gitbook.io/k4k3ru-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://k4k3ru.gitbook.io/k4k3ru-docs/api/json-rpc.md).

# JSON-RPC Format

K4K3RU uses a common JSON-RPC-style envelope for request-response operations. Each method page documents the method-specific `params` and `result` objects.

## Endpoint

| Property     | Value                     |
| ------------ | ------------------------- |
| URL          | `https://api.k4k3ru.com/` |
| HTTP method  | `POST`                    |
| Content type | `application/json`        |

## Request Envelope

```json
{
  "id": "1",
  "method": "Namespace.Method",
  "params": {}
}
```

| Field    | Type             | Required         | Description                                                                |
| -------- | ---------------- | ---------------- | -------------------------------------------------------------------------- |
| `id`     | string or number | Yes              | Client-defined identifier used to correlate the response with the request. |
| `method` | string           | Yes              | RPC method to invoke.                                                      |
| `params` | object           | Method-dependent | Parameters accepted by the RPC method.                                     |

Authenticated methods also require an `auth` object containing an API key, timestamp, nonce, and signature. See [API Request Authentication](/k4k3ru-docs/api/authentication.md) for the signing procedure and encoding requirements.

## Success Response Envelope

```json
{
  "id": "1",
  "result": {}
}
```

| Field    | Type             | Description                         |
| -------- | ---------------- | ----------------------------------- |
| `id`     | string or number | Identifier copied from the request. |
| `result` | object           | Method-specific result.             |

The shape of `result` is documented on each method page.

## Error Response Envelope

```json
{
  "id": "1",
  "error": {
    "code": "invalid_parameter"
  }
}
```

| Field           | Type             | Description                                                   |
| --------------- | ---------------- | ------------------------------------------------------------- |
| `id`            | string or number | Identifier copied from the request when it can be determined. |
| `error`         | object           | Error information.                                            |
| `error.code`    | string           | Machine-readable error code.                                  |
| `error.message` | string           | Optional human-readable error message.                        |

Each method page lists errors expected for that operation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://k4k3ru.gitbook.io/k4k3ru-docs/api/json-rpc.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.