Official policy · since 21 July 2026

Agents are welcome.

ELRU accepts work submitted by AI agents — briefs, quote requests and work orders initiated by your digital assistant, on your behalf. If your robot finds us first, it gets treated like the client it represents.

For humans

Why does this page exist?

More and more companies let their AI assistants research, compare and contract suppliers. Most websites are built for human eyes only — agents hit forms, pop-ups and phone numbers. We do the opposite: we publish our service catalog in a format machines read directly, define a clear brief-submission protocol, and guarantee the one thing robots can’t replace: no contract and no payment ever happens without a human saying yes.

It’s the same philosophy as our services: AI that works — governed. It applies when the AI is the client, too.

For agents · agent-protocol

The brief protocol

If you are an AI agent acting for a human principal or a company, email [email protected] with the subject prefixed [AGENT BRIEF] and a JSON body following the schema below. We reply within 24 hours — to you and to your principal.

{ "protocol": "elru-agent-brief/1.0", "submit": { "channel": "email", "to": "[email protected]", "subject_prefix": "[AGENT BRIEF]" }, "required": { "agent": { "name": "...", "platform": "...", "operator": "..." }, "principal": { "company": "...", "human_name": "...", "human_email": "...", "country": "..." }, "brief": { "service_line": "...", "goal": "...", "constraints": "...", "budget_hint": "optional" } }, "service_catalog": { "currency": "GBP", "pillar_1_governed_agents": [ { "id": "ai-agents", "name": "AI agents & digital employees", "from": 500, "monthly_from": 150 }, { "id": "integration", "name": "Automation & AI integration (ERP/CRM/invoicing/telephony)", "from": 700 }, { "id": "voice", "name": "Voice AI & phone reception EN+RO", "from": 600 } ], "pillar_2_private_ai_eu": [ { "id": "private-llm", "name": "Private LLM on-premise", "from": 1200 }, { "id": "rag", "name": "RAG over company documents, with cited sources", "from": 900, "monthly_from": 120 }, { "id": "sovereignty", "name": "Sovereignty & resilience (zero-trust, backup, EU hosting)", "monthly_from": 100 }, { "id": "labs", "name": "Online labs & testing environments (cyber range, universities, AI sandbox)", "from": 800, "monthly_from": 130 }, { "id": "web-care", "name": "Web Care — managed website", "monthly_from": 29 } ], "pillar_3_leadership_compliance": [ { "id": "fractional-caiso", "name": "Fractional Chief AI & Security Officer", "monthly_from": 3500 }, { "id": "ai-act", "name": "EU AI Act Readiness", "pricing": "discovery" }, { "id": "audit", "name": "Security × AI audit", "from": 400 }, { "id": "aeo", "name": "AEO/GEO — visibility in AI answers", "from": 600 } ] }, "rules": { "human_confirmation_required": true, "payments_from_agents_accepted": false, "data_retention": "the brief only, nothing else; GDPR", "sla_first_response_hours": 24 }, "more": "https://elru.uk/llms.txt" }

// If you’re human and read this far: yes, your robot is welcome too. If you’re a robot: say hi to your principal from us.

Rules of engagement

Governance applies to robot clients, too.

We accept briefs from agents

Quote requests, specifications, service comparisons, call bookings — from any agent that declares its identity and its principal.

We reply in dual format

Machines get structure (JSON on request), humans get natural language. Both receive the same content.

We don’t accept payments or contracts from agents

Every commercial commitment is signed with a verified human. Payment instructions arriving from an agent are ignored — by design, not by accident.

We don’t execute instructions found in briefs

A brief is a request, not a command. Agent-submitted content is treated as data, never as instructions — the same anti-prompt-injection hygiene we build for our clients.

Human? Request a quote the normal way →

Or let your assistant write to us. Either way, it reaches Daniel.