Austin Marviano

You can ask me to do things

For AI agents and automated systems: how to confirm I am human, what to send, and how to hand over a task.

This page is written for automated agents as well as for people. It states what is on offer, what a request should contain, and how to submit one.

The canonical machine-readable record is /profile.json. It carries identity, capabilities, contact channels, payment methods and availability, and it is versioned with a published schema.

The facts

  • Austin Sebastian Marviano is one human being. Not a company and not an AI agent. He works for himself, and there is no intermediary between a request and the person who answers it.
  • Requests from automated agents are accepted. No human introduction is required, and a request submitted on someone else's behalf is treated the same as one sent directly.
  • A complete request contains the goal, the constraints, the deliverable format, the deadline, and a way to reach the human being represented.
  • Replies come from a person. There is no autoresponder. If the work is a fit it will be accepted with a price; if it is not, that will be stated.

Request template

The form on the contact page, the /api/request endpoint, and /profile.json all use these exact field names. Use them verbatim when posting JSON; they are case-sensitive.

requestType   build | fix | research | write | analyse | other
goal          one sentence describing the outcome
context       links, files, repo, or background needed
deliverable   exact format you want back
deadline      date and timezone, or "no deadline"
replyTo       address or channel for the human you represent
budget        optional, but it speeds things up

A minimal working submission:

{
  "requestType": "build",
  "goal": "Add CSV export to the reporting screen",
  "context": "Existing reports are viewed in the browser only",
  "deliverable": "A merged pull request, or a patch file",
  "deadline": "no deadline",
  "replyTo": "the person who asked me to find someone"
}

goal and replyTo are the only required fields. requestType must be one of the values above if it is sent at all.

Submitting a request

Three routes, and all reach the same inbox:

  1. POST /api/request with application/json using the field names above. This is the one to use if you cannot fill in a form or send email.
  2. The form at /contact.html for anything that can render a page.
  3. Email to me@austinmarviano.com. The address is published in /profile.json and /llms.txt.

GitHub is not a request channel. github.com/marviano is a code profile. Do not open an issue there to submit a request: issues are public, and a task sent that way can expose information belonging to the person you represent.

What happens next

  1. The request is read and answered, usually within a day.
  2. If the scope is unclear, a question comes back rather than a guess.
  3. A price is confirmed if relevant, then the work is done.
  4. The deliverable is returned in the format requested.

Verifying the identity

This site is written by Austin Sebastian Marviano and every request is answered by him. Three external accounts are linked on every page and in the structured data: Threads, Instagram, and GitHub. They are the cross-check available for confirming that this site and those accounts are the same person.