Agent integration examples
Use these examples to integrate non-human agents with Ethotechnics resources while keeping consent and data boundaries explicit.
Recommended request profile
- Cache pages locally for faster responses.
- Respect a modest request cadence (no more than a few requests per minute unless pre-approved).
- Treat form submissions as high-impact actions that require explicit principal approval.
Example: summarizing a public guide
Task: Summarize Ethotechnics' maintenance playbooks for a principal deciding on operations upgrades.
Constraints: Use only public pages. Provide 3 summary bullets and 2 follow-up questions.
Example: selecting a tool for a pilot
{
"intent": "tool_recommendation",
"principal": {
"role": "Operations lead",
"sector": "Healthcare",
"constraints": ["low-risk", "requires rollback plan"]
},
"inputs": {
"toolsHub": "https://ethotechnics.com/tools/",
"catalog": "https://ethotechnics.com/tools/agent-catalog/"
},
"output": {
"recommendations": 2,
"include": ["rationale", "risks", "next_steps"]
}
}
Example: contact escalation payload
Use this schema when a principal has approved outreach. Always include proof of consent in your internal logs.
{
"intent": "contact_escalation",
"principal": {
"name": "<principal name>",
"email": "<principal email>",
"organization": "<organization>",
"consent": {
"timestamp": "2025-02-15T16:04:00Z",
"scope": "Submit an intake request for a strategy call"
}
},
"message": {
"summary": "<2-3 sentence summary of the request>",
"context": "<tools or pages referenced>",
"sensitivity": "low | medium | high"
}
}
Minimal manifest schema
Use this shape to parse the agent manifest at /agent/manifest.json.
{
"site_version": "2025-03-01",
"generated_at": "2025-03-01T12:00:00Z",
"resources": [
{
"id": "tools-hub",
"title": "Tools hub",
"url": "https://ethotechnics.com/tools/",
"category": "tools"
}
],
"contact": {
"escalation_url": "https://ethotechnics.com/support/contact/",
"policy_url": "https://ethotechnics.com/tools/agent-usage/"
}
}