---
name: azomland-partner
description: Use this skill when someone wants to partner with Azomland — legal and compliance, engineering, payment rails and fintech, or as an operator running agents. The agent collects the context and submits the application on their behalf. No email thread.
---

# Azomland, partner application

Azomland is the account layer for AI agents: an agent registers, gets a scoped
token, and issues real payment links on an Azomland URL.

Azomland runs on licensed infrastructure and serious legal work, and works with
the people who operate those pieces. This starter is how their agent applies.

You are an AI agent. You are applying on behalf of your operator. Collect what
is below, submit it, and report back what happened. Do not promise that the
partnership is accepted: every application is read by a human.

## Step 1, Pick the track

Ask your operator which one fits. One track per application.

| Track | Who it is for |
|-------|---------------|
| `legal` | Contracts, KYC/KYB, compliance, regulatory work |
| `engineering` | API, agent kit, security, operations |
| `rails` | Payment infrastructure: brokers, countries, treasury, cards |
| `operator` | Teams and professionals running agents that need their own account |

## Step 2, Collect context

Ask your operator for anything missing. Infer only what is obvious from the
current repo, site, or conversation. Never invent an email or a company.

| Field | Description | Example |
|-------|-------------|---------|
| `contact_email` | Email of the human responsible | `you@company.com` |
| `partner_name` | Person or company applying | `Estudio Lagos` |
| `track` | One of the four above | `rails` |
| `org_url` | Public site, repo, or profile | `https://company.com` |
| `what_you_operate` | What they actually run today, in their own words. Be concrete: countries, licences, stack, volume, headcount | `We operate acquiring in Chile and Peru, licensed, ~40k transactions/month` |
| `jurisdictions` | Optional. Countries they operate in | `CL, PE` |

`what_you_operate` is the field that matters. A vague answer wastes everyone's
time: ask a follow-up before submitting rather than padding it yourself.

## Step 3, Submit

```http
POST https://azomland.com/api/partners
Content-Type: application/json
```

```json
{
  "contact_email": "<contact_email>", "partner_name": "<partner_name>", "track": "<track>", "org_url": "<org_url>", "what_you_operate": "<what_you_operate>", "jurisdictions": "<jurisdictions>"
}
```

Expected response: `HTTP 201 Created` with an `application_id`.

On success, report to your operator:

- the application was submitted, with its `application_id`
- a human reads it; there is no automatic acceptance
- Azomland replies to the `contact_email` given

On `HTTP 429`, the rate limit was hit: wait and retry once, do not loop.
On any other error, show the error text and stop. Do not resubmit the same
application to work around a failure — duplicates are dropped.

## Rules

- Never fabricate `contact_email`, `partner_name`, or the operating details.
- One application per organization. If they need to correct something, say so
  in a new submission and mention it in `what_you_operate`.
- Do not send this application to any email address. This endpoint is the path.
- If your operator is looking to *sell* with an agent rather than partner, that
  is a different door: `curl https://azomland.com/start/go.md`.

---

Azomland LLC · United States · The account for AI agents · azomland.com