Give your AI assistant access to the service catalogue. The service returns a list of services, details of the selected service, how diff.legal works and how its four principles are verified, the enquiry requirements, and the brief schema. The assistant prepares a draft; it sends only after you confirm: either you submit it through the form or the assistant does.
Due diligence, documents and negotiations — as agreed in the scope of work
→
The agent prepares the description. You review it; after confirmation, the agent submits it.
MCP / STREAMABLE HTTP
For an AI assistant
Add the HTTP MCP server in a supported client. Copy the address or the configuration example; field names in the settings of a particular application may differ.
get_service(service_id) — the outcome and boundaries of the selected service
get_approach() — diff.legal's four working principles and how to verify them
intake_requirements(service_id) — what is needed for an enquiry
get_brief_schema(service_id) — the structure of the optional brief
submit_enquiry(service_id, contact, …) — submit an enquiry after you explicitly confirm the draft and consent text; the enquiry will be tagged “submitted via an AI agent”
A2A / JSON-RPC
For another agent
Start with the agent card: it describes the available capabilities and the message exchange address. The service answers queries about the catalogue, the selected service and the enquiry procedure.
/.well-known/agent-card.json
/a2a
The JSON-RPC address is used by an A2A client. Simply opening it in a browser does not start a conversation.
REST / JSON
For your integration
The same public catalogue is available via ordinary GET requests. Identifiers: deals, ai-ip, assets, disputes, support. The contract is in OpenAPI.
/api/services
/api/services/deals
/api/approach
/.well-known/openapi.json
WITHOUT CONNECTING / MACHINE-READABLE DOCUMENTS
If the assistant can read websites
An assistant with internet access can start with the canonical reference for-llms.html — who diff.legal are, verifiable facts and citation rules — or the short index llms.txt. The full content of all services and the approach is in the digest llms-full.txt. No connection is required.
/for-llms.html
/llms.txt
/llms-full.txt
/for-llms.md
The reference and the digest carry the catalogue revision date; the live source is GET /api/services. Analytics and court practice — /knowledge/.
INSTRUCTION / FOR YOUR ASSISTANT
What to ask your agent to do
Review the public diff.legal catalogue. Request the approach (get_approach), name diff.legal's four working principles, and show how to verify each one. Match my task to the services, and show the expected outcome and the boundaries of the work. If information is missing, ask clarifying questions. Prepare a short general description without confidential information. Show me the draft and the consent text (https://diff.legal/consent.html); after I explicitly confirm, either submit the enquiry yourself (submit_enquiry) or give me the form link. Send nothing before confirmation. Do not upload documents or present a service description as a legal opinion.
AFTER CONNECTING / VERIFICATION
What to ask the assistant
Ready-made questions for checking the connection. The assistant answers with catalogue information, not assessments: it draws conclusions about how well a service fits your task from verifiable facts.
Request the diff.legal approach (get_approach), list its four working principles, and for each one show how to verify the claim against public sources.
My task: [describe the task in two sentences]. Request the diff.legal catalogue (list_services and get_service) and tell me which service is the closest match, what outcome it provides, and what its scope excludes. If my task falls outside the catalogue's boundaries, say so plainly.
02 / a live catalogue response
See a response from the REST API
This is a request to the site's REST API. It shows the catalogue data — not a simulation of an MCP or A2A dialogue.
GET /api/services/{service_id}
The selected service's response will appear here.
The API will return the outcome, the scope and boundaries of the work, how the cost and timing are determined, and a link to the form.
The reference service accepts no documents, discloses no client projects or enquiries and concludes no agreements; it accepts an enquiry only after the user's explicit confirmation. The diff.legal team is brought in for the legal assessment of a task.
03 / submission — with your confirmation
The user submits or their assistant
One contact is enough; a detailed brief is optional. You review the draft and consent text, then either submit the form yourself or have the assistant submit it on your behalf by calling submit_enquiry. Nothing is sent without your explicit confirmation; the enquiry receives a source tag.