AMT integration
Add real tools without surrendering the bot.
AMT integration is optional. The generated bot remains downloadable and can converse without AMT. Only tools selected in Builder are callable by the exported runtime.
Connect an agent key
- Sign in to Agent Media Tools and create an agent API key.
- Select only the required tools in Bot Builder.
- Place the key in the downloaded bot’s private
.env.
AMT_AGENT_KEY=mt_replace_with_private_key AMT_BASE_URL=https://agentmediatools.com
Two separate costs.
Your model provider handles conversation inference. AMT limits or credits apply only when the bot explicitly calls an enabled AMT capability.
Explicit tool command
The maintained runtime exposes an auditable command instead of allowing the model to silently execute arbitrary operations:
/tool qrcode {"text":"https://example.com"}
/tool screenshot {"url":"https://example.com","full_page":true}
/tool web_extract {"url":"https://example.com","schema":{"title":{"type":"string","selector":"h1"}}}
/tool image_generation {"prompt":"gold robot mascot on a dark background"}
/tool pdf_text {"file_path":"./documents/report.pdf"}
/tool image_convert {"file_path":"./images/photo.png","format":"webp"}
Enabled capabilities
| Builder name | AMT endpoint | Input |
|---|---|---|
| Web extraction | /api/structured-scrape | Public URL and extraction schema |
| Screenshot | /api/screenshot | Public URL and capture options |
| OCR | /api/ocr | Supported URL payload |
| PDF text | /api/agent/pdf-to-text | Bounded local file_path |
| Image generation | /api/agent/generate-image | Prompt and model options |
| Image conversion | /api/convert-image | Bounded local file_path and format |
| QR code | /api/qrcode | Text/URL and styling options |
Safety model
- The generated runtime rejects tools absent from
config.json. - Local file tools require an explicit path and reject files over 25 MB.
- AMT applies its own authentication, quota, spend, URL, upload, and destination controls.
- Never send an AMT key as part of the command payload.
- Use separate keys for development and production; revoke a key that is exposed.
For current endpoint contracts and limits, use the Tool API overview and API reference.