Give your AI assistant access to the service catalog. The server returns services, details of a selected service, the diff.legal approach and evidence for its four principles, intake requirements and a brief schema. The assistant helps select a service and provides a form link. You review the information and submit the enquiry yourself with separate consent.
Due diligence, documents and negotiations — as agreed in the scope of work
→
The agent prepares the description. You review it and submit the form yourself.
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, offer_id) — obtain a safe link to the human form, without creating an enquiry. Supply only public service_id and offer_id; do not supply contacts or private information
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, ai-transformation. 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
Read the public diff.legal catalog. Request the approach (get_approach), name the four principles and explain how to check each one. Match my task to the services and show expected results and scope boundaries. Ask questions if information is missing. Prepare a short general description without confidential information. Show me the draft and consent text (https://diff.legal/consent.html); give me a safe form link through submit_enquiry. I will enter the information, confirm separate consent and submit the enquiry myself. Do not send contacts or private information to tools. 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 via the form
One contact is enough; a detailed brief is optional. The person reviews the draft and consent text, then submits the form themselves with separate consent. submit_enquiry returns only a safe link and sends nothing. A form found through an assistant carries a source marker.