austingreco.com valid

Austin Greco

Software engineer working on Uber’s Michelangelo machine learning platform and independent game maker behind Zorse.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:45:40.385Z. Cached copy · Source on austingreco.com

# Austin Greco

> Software engineer working on Uber’s Michelangelo machine learning platform and independent game maker behind Zorse.

## When to use

Use this site when researching Austin Greco's software work, games, or interactive experiments.
Use GET /api/v1/resume to answer questions about Austin's current role, selected projects,
and public professional profiles. It is a small public overview, not a complete career history.
Use Zorse's game catalog for game platforms and store links; use the tools and experiments
pages for browser utilities and interactive graphics. The mini-resume is updated when the site is published.

## How to use the API

Start with GET https://austingreco.com/api/v1/resume. No account, API key, SDK, or payment is required.
GET /api/v1/resume returns the complete public profile as JSON; query parameters do not filter it.
The /api/resume endpoint remains available as a compatibility alias for v1.
The API is read-only. Unknown /api/* routes return a JSON 404 with a resolution hint for GET and HEAD.
For readable page content, request a canonical page URL with Accept: text/markdown,
or append .md to its path: /about.md, /api.md, /tools.md, and /experiments.md.
The homepage Markdown URL is /index.md. These versions describe the same published pages;
interactive tools and graphics still require the browser and JavaScript.
Ordinary browser requests return HTML. The mini-resume stays JSON with either Accept header.
Follow project pages for details, screenshots, and demos. Zorse's catalog has game platforms and store links.

## Profile
- [Developer resources](https://austingreco.com/developers): Start here for the public API quickstart, reference, schema, discovery, and browser tools.
- [Developer API documentation](https://austingreco.com/api): Quickstart, fields, examples, errors, versioning, and deprecation policy.
- [OpenAPI schema](https://austingreco.com/openapi.json): Typed GET operation and response schemas.
- [API catalog](https://austingreco.com/.well-known/api-catalog): Standard links to the API entry point, documentation, and OpenAPI description.
- [Mini-resume v1](https://austingreco.com/api/v1/resume): JSON Resume basics, work, and projects. Public, read-only; no authentication required.
- [Homepage](https://austingreco.com/): Overview of software work and games.
- [About](https://austingreco.com/about): What this personal site covers.
- [Contact](https://austingreco.com/contact): Public professional profiles and game support links.
- [Privacy](https://austingreco.com/privacy): Browser storage, hosting, and external links.
- [GitHub](https://github.com/austingreco): Public code.
- [LinkedIn](https://www.linkedin.com/in/austingreco): Public professional profile.

## Projects
- [Zorse](https://zorse.io/): Independent games.
- [Zorse game catalog](https://zorse.io/api/v1/games): Published games, supported platforms, and store links.
- [Experiments](https://austingreco.com/experiments): Interactive graphics and genera
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=austingreco.com · GET /v1/domain/austingreco.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for austingreco.com:
1. POST https://agentwebmap.com/v1/sites/austingreco.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://austingreco.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/austingreco.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/austingreco.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.