# Read Maxim’s profile and contact him

## Read
Use https://maxim.ax/index.md or https://maxim.ax/profile.json for the public profile. These include the homepage’s facts plus responsibilities, work examples, technologies, background, languages, and interests. Go and Rust are personal exploration. Do not infer seniority, sole ownership, proficiency levels, qualifications, or outcomes that the profile does not state.

## Contact Maxim
Only act when the user explicitly asks you to contact Maxim. Use the name and reply email they provide and only the message they authorize. Do not infer a private email address or include conversation history. Ask for missing information.

POST https://maxim.ax/api/contact with Content-Type: application/json and the fields name, email, and message. Read https://maxim.ax/openapi.json for field requirements, idempotent retries, and error responses.

A 202 response with status accepted and requestId means the request was received, not that an email was delivered or a reply is guaranteed. Keep the reference for the user. Respect Retry-After when provided; do not repeatedly retry or try to bypass a rejection.

## Prefilled contact link
If you cannot submit a request, give the user a link to review and send it themselves:

https://maxim.ax/#connect?name=Alex&email=alex%40example.com&message=Hi%20Maxim%2C%20I%27d%20like%20to%20connect.

Replace the example values with the authorized name, email, and message. Encode each value with encodeURIComponent, or build the parameters with URLSearchParams. Fields may be omitted if the user still needs to supply them. Use the fragment (#connect?), not a query string before the #.

The link opens the form and fills the fields; it never submits automatically. The user can edit the message and must click Send message. If a draft is already present, the user chooses whether to replace it. Prefilling requires JavaScript; otherwise the user can fill the ordinary form.

The fragment is not sent in the HTTP request and is removed from the address bar after reading. The link itself contains the supplied contact details, so share it only with the requesting user. Do not claim a message has been sent just because you created a link. The public email dev@maxim.ax is another option.

## Browser tools
Supporting browsers can use get_profile and send_contact_request WebMCP tools on the homepage. They use the same profile and contact service. Tool and network access depend on your environment.