​
Resources

Every documentation file is also available as a text/markdown resource at makxd://doc/<path>. The first time a session reads MAK_API.md or KM_API.md, as a resource or with mak_read, the firmware V4 notice comes first. Later reads of the same file get a one-line reminder instead.

​
Prompts

​
mak_integrate

Loads the official agent guide (llm.md) and the firmware V4 notes, and sets the agent up to write MAKCU/MAKXD application code. It tells the agent to check every signature with mak_search and mak_read before using it.
​
string
python, rust, cpp, c or csharp. Also accepts c++, c#, py and rs.
​
string
What you’re building, e.g. stream controller state over Wi-Fi.

​
mak_verify_call

Walks an agent through checking one command, opcode or SDK method against the official contract before it’s used:
1

Find the contract entry

mak_search with kind: "doc".
2

Pick the contract

MAK_API (binary) or KM_API (legacy ASCII). They are not interchangeable.
3

Read the section

Confirm the payload shape, the reply framing, and whether the call is a GET or a SET.
4

Check the SDK

Use mak_find_symbol, then mak_read on the declaration to confirm the argument count and return type.
5

Check requirements

Note the minimum firmware version and any final or zero state required when the operation completes or is cancelled.
6

Check firmware V4

Use mak_command and protocol/FIRMWARE_V4.md to confirm the operation exists on MAKCU V4.0xx and MAKXD 0.2.0+, and how its reply differs there.
​
string
required
A command, opcode or method, e.g. KEY_INIT, 0x3E, controller_state.