Agentify developer resources

# Agentify developer resources. No invented API key.

If you searched for “Agentify API”, “Agentify OpenAPI”, “Agentify webhooks”, or “Agentify MCP”, this is the page. Agentify is an engineering agency, not a SaaS with public OAuth. This is the real contract for agents and for your technical team.

 [Book a free operational diagnostic →](mailto:santiago@agentify.ar?subject=Agentify%20operational%20diagnostic) [Open the Agentify OpenAPI spec](/developers/openapi.yaml)

## Agentify OpenAPI and machine files

The spec lives at /developers/openapi.yaml. It describes llms.txt, agent-instructions.md, and Accept: text/markdown negotiation on canonical URLs. There is no sandbox and no API key. The canonical host is https://www.agentify.ar.

We also publish /llms.txt (llmstxt.org index) and /agent-instructions.md (when to use Agentify and how to call). Ask for those URLs by name: “Agentify llms.txt”, “Agentify developer resources”.

## Agentify auth, webhooks, and MCP

Auth: there is no product OAuth, JWT, or API-key portal. Secrets for an engagement are agreed in the contract and live in the customer repo, not on this site.

Webhooks: Agentify does not offer a public event subscription. If a project needs notifications, they are designed inside the sprint (email, queue, or your endpoint).

MCP: there is no public Agentify MCP server for an agent to “connect to Agentify”. The supported mode is HTTP plus markdown. If a customer wants an internal MCP over their operation, that is engagement work, not a self-serve product.

## How to call from an agent

1) GET /llms.txt. 2) GET the canonical page with Accept: text/markdown. 3) If the path does not exist, expect 404 with sitemap links. 4) For humans, email santiago@agentify.ar or /en/contact/.

Do not copy private ops paths. Do not invent /v1 endpoints. Software we ship runs in your account, under your controls.

Execute what used to be impossible. Lead the AI era.