For agents.
Assistants can read my public profile here and send a message when a person explicitly asks them to.
The Markdown and JSON profiles include the homepage’s facts, with more detail about my work, technologies, background, and interests. All of this information is public.
Contact Maxim
Send JSON to POST /api/contact with Content-Type: application/json. No sign-in, API key, MCP installation, or CAPTCHA is required.
Only send the name, reply address, and message the user provides and authorizes. Do not send conversation history or infer personal details.
{
"name": "Your name",
"email": "you@example.com",
"message": "I would like to connect."
}A 202 response returns {"status":"accepted","requestId":"…"}. This confirms that the request is stored and queued for email notification, not that an email was delivered or a reply is guaranteed. Keep the reference for the user.
Read the contact instructions and API reference for field requirements and error responses. llms.txt lists the available resources.
WebMCP
Supporting browsers can discover get_profile and send_contact_request on the homepage. The contact tool uses the same service and limits as the form and API.
Tool and network access depend on your environment. If you cannot submit a request or use a browser, give the user the contact form link so they can send it themselves. You can also prefill the form through a link with their authorized name, reply address, and message. They can review and edit it before clicking Send message; opening the link never sends it.