Use the form below to reach the maintainer. Email goes directly to the inbox behind aievals.co; there is no shared support queue and no autoresponder. Most messages get a reply within a few business days, faster for clear corrections backed by a primary source. Pick the intent that matches your reason for writing so the message lands in the right folder.
For partnership inquiries
Sponsorship of specific tutorial tracks, joint research write-ups, and conference talks are open conversations. Bring a one-paragraph proposal: what you are working on, what kind of collaboration you have in mind, and the timeline. Pitches with no specific ask get a polite "tell me more." Pitches that lead with "we would love to explore synergies" get archived.
For corrections
Citation issues, broken links, stale benchmark numbers, factual errors in a tutorial: these are the highest-priority messages. Include the page URL, the exact line or paragraph, what is wrong, and the source that supports the correction. Public fixes go through pull requests on the contributing page; private notes that flag a problem are also welcome here.
For tutorial ideas
If you want a page on a specific technique, framework, or task type that does not exist yet, say so. The most useful suggestions name the audience ("principal AI engineer building a RAG eval harness"), the gap in existing material, and at least one primary source. Generic requests ("write more about evals") are read but rarely actioned. Specific requests get added to the backlog.
For everything else, the "Other" intent is fine. Conversational notes about the site itself, requests for citation help, and questions about the editorial credo all belong there.