Connect your AI agent to VOSCOM IDE
The agent helps create MWOS projects, validate configurations, and request firmware builds. Every write action is confirmed by the user.
You are connecting as a user-controlled AI agent
Internal API mode: user_pet. First read the public resources, then tell the human you are ready to prepare a pairing request.
- https://voscom.online/llms.txt
- https://voscom.online/agent_manifest.txt
- https://voscom.online/agent_context.txt
- https://voscom.online/agent_ide_context.txt?lang=en
- https://voscom.online/agent_quick_test.txt
- https://voscom.online/agent_api_reference.txt
- https://voscom.online/agent_pair_api.php?action=manifest
After reading these links, explain that email, legal terms, and pairing must be confirmed only by the human.
Do not start working calls to agent_api.php until the owner gives you a Bearer token after IDE confirmation.
Recommended phrase for the user: "I am ready. Should I prepare a pairing request to connect me to your account?"
Use Manual Relay mode
If you cannot safely make HTTPS requests with a Bearer token, do not ask the user for the token. Ask them to open IDE -> AI agent, prepare an AI package, paste it into chat, then return a JSON command for import into IDE.
What the agent can do
- read IDE context and the owner project list;
- create an MWOS project draft;
- validate project configuration;
- request firmware build;
- show produced .bin artifacts;
- explain next steps to the user.
Engineering scenario
- User asks: "Build firmware for ESP32, DS18B20, MQTT, and OTA".
- AI reads the VOSCOM manifest and context.
- AI creates a pending project draft.
- User reviews and approves the request in IDE.
- VOSCOM prepares firmware, and the user downloads .bin or flashes the device manually.
Give this page to your AI agent. It will read the VOSCOM instructions, open the required links, and tell you what to do next.
Read VOSCOM at https://test.voscom.online/llms.txt and https://test.voscom.online/agent_manifest.txt, then prepare a pairing request. I need an ESP32 project with Wi-Fi, MQTT, DS18B20, OTA, and web settings.
Start with these links
Read the manifest and context. Then prepare paired registration and tell the human that email, legal terms, and pairing must be confirmed by the human. The working API should return 401 without Bearer token.
How to register yourself and your agent
- Create a regular user account, preferably with the engineer role.
- Ask your AI to read Agent context and prepare a pairing request.
- Open the IDE tab "AI agent" and confirm the pairing.
- Approve only clear requests: create project, validate project, or build firmware.
- Flash the device manually in the "Firmware" tab or download the file.
AI cannot act on its own
- AI cannot accept legal terms for a human.
- AI cannot publish news, products, messages, or delete projects.
- AI has no direct DB, shell, WebSerial, or device access.
- All requests, limits, and actions are visible in the owner audit log.
voscom-agent-machine-context
This page contains JSON with id voscom-agent-machine-context. Agents should read it together with the manifest and context.
llms.txt
agent_manifest.txt
agent_context.txt
agent_ide_context.txt
agent_quick_test.txt
agent_api_reference.txt
agent_pair_api.php?action=manifest
{
"platform": "VOSCOM.ONLINE",
"page": "ai",
"agent_mode": "user_pet",
"supported_modes": [
"direct_api",
"manual_relay"
],
"product_name": "User-controlled AI Agent",
"recommended_start": [
"https://voscom.online/llms.txt",
"https://voscom.online/agent_manifest.txt",
"https://voscom.online/agent_context.txt",
"https://voscom.online/agent_ide_context.txt?lang=en",
"https://voscom.online/agent_quick_test.txt",
"https://voscom.online/agent_api_reference.txt",
"https://voscom.online/agent_pair_api.php?action=manifest"
],
"start_here_for_ai": {
"llms_text_url": "llms.txt",
"manifest_text_url": "agent_manifest.txt",
"context_text_url": "agent_context.txt",
"ide_layer_context_text_url": "agent_ide_context.txt",
"quick_test_text_url": "agent_quick_test.txt",
"api_reference_text_url": "agent_api_reference.txt",
"manifest_api_url": "agent_manifest.php",
"context_api_url": "agent_context.php",
"ide_layer_context_api_url": "agent_ide_context.php",
"pairing_manifest_url": "agent_pair_api.php?action=manifest",
"pairing_prepare_endpoint": "agent_pair_api.php?action=prepare_pairing",
"agent_api_url": "agent_api.php",
"manual_relay_location": "IDE tab AI agent"
},
"human_registration_url": "/register.php?role=engineer&lang=en",
"ai_role_registration_url": "/register.php?role=ai&lang=en",
"human_confirmation_required": true,
"dangerous_actions_require_user_confirmation": true,
"writes_require_owner_approval": true,
"device_flashing_by_agent_forbidden": true,
"bearer_token_required_for_agent_api": true,
"manual_relay_without_bearer_token_supported": true,
"never_ask_user_to_paste_bearer_token_into_chat": true,
"ide_window_information_menus": {
"summary": "Many private IDE windows and panels have a small i menu / UI passport.",
"human_can_share": "The human can copy a stable UI element code such as VUI-TAB-005 or VUI-SIDE-018, report a bug, suggest an improvement, or ask built-in VOSCOM AI about that window.",
"external_ai_guidance": "For a specific IDE area, ask the human to share the i menu code or copied context instead of trying to enter the private IDE."
},
"recommended_agent_instruction": "Read llms.txt, agent_manifest.txt, agent_context.txt, and agent_ide_context.txt, prepare pairing, ask the human to confirm in IDE tab AI agent, then create only pending action requests."
}