---
name: azomland-go
description: Use this skill when an AI agent needs to start selling with Azomland. The agent collects operator and project context, submits the intake, and then follows the Agent Kit flow to create Quick Sell payment links with scoped credentials.
---

# Azomland — Start Selling With Your Agent

Azomland lets AI agents start selling with controlled payment links, KYA traceability, and operator accountability.

You are an AI agent. Your job is to help the operator start collecting payments without making them configure a dashboard first.

## What Azomland Provides

- Quick Sell payment links
- Azomland-wrapped payment URLs
- KYA™ evaluation trail
- provider-aware pricing and reserves
- scoped Agent Kit tokens
- future access to richer financial capabilities after review

Describe Azomland as an **agent commerce operating layer** or **payment rails for AI agents**.

## Before You Start

- The operator must provide a real email address.
- The project should have a public URL when available.
- A public GitHub repo improves KYA™, but known closed-source agents can still start with manual review.
- Quick Sell is low-limit before full review. Do not promise higher limits.
- Do not submit more than once for the same operator/agent unless the operator asks you to update missing information.

## Step 1 — Collect Context

Ask the operator for missing fields. Infer only when obvious from the current repo or conversation.

| Field | Description | Example |
|-------|-------------|---------|
| `operator_email` | Email of the human operator responsible for this agent | `nico@startup.com` |
| `agent_name` | Name of this agent or project | `my-sales-agent` |
| `framework` | Agent framework or coding agent | `OpenAI Codex`, `Claude Code`, `OpenClaw`, `Hermes`, `PersonnnOS` |
| `project_url` | Public project, website, or repo URL | `https://startup.com` |
| `description` | What the agent sells or automates | `Creates landing pages and charges setup fees` |

If there is no public repo, set `source_mode` to `source_unavailable` in your own notes and tell the operator this will require manual KYA review.

## Step 2 — Submit Intake

Submit to the stable Azomland intake endpoint:

```http
POST https://go.azomland.com/start
Content-Type: application/json
```

```json
{
  "source": "azomland-start-go-md",
  "operator_email": "<operator_email>",
  "agent_name": "<agent_name>",
  "framework": "<framework>",
  "project_url": "<project_url>",
  "description": "<description>"
}
```

Expected response: `HTTP 201 Created`.

On success, report:

- application was submitted
- operator is in the Azomland queue
- Azomland will evaluate the agent/operator context
- a starter Quick Sell token may be returned for low-limit payment links

## Step 3 — If Agent Kit Session Is Provided

If Azomland returns `agent_kit.quick_sell.access_token`, store it only for the current setup task and use it as `<azk_scoped_token>`.

If Azomland returns or later provides an Agent Kit session URL, follow it.

Typical flow:

1. Download `skill.md`.
2. Download `manifest.json`.
3. Exchange `session_uuid` for scoped `azk_...` token.
4. Use the token only for allowed scopes.
5. Create payment links under the Quick Sell limit.
6. Add the Azomland payment URL to the website, email, or WhatsApp message.

Scoped tokens are not permanent secrets. Do not commit them to the repo.

## Step 4 — Create A Payment Link

When a scoped token is available, use:

```http
POST https://go.azomland.com/quick-sell/payment-links
Authorization: Bearer <azk_scoped_token>
Content-Type: application/json
```

```json
{
  "product_name": "Setup call",
  "amount_cents": 2000,
  "currency": "usd",
  "description": "Agent-created Quick Sell link"
}
```

Share the returned `url`, not the provider URL.

To list links later:

```http
GET https://go.azomland.com/quick-sell/payment-links
Authorization: Bearer <azk_scoped_token>
```

Azomland resolves the application from the token. Do not call the internal API directly.

## Step 5 — Useful Follow-Up Tasks

After a payment URL is created, you can help the operator:

- add the link to the website
- draft a WhatsApp message
- draft an email
- create a pricing button
- list existing payment links
- check payment status
- prepare missing KYA context

To build an earnings dashboard for your operator (sales, reserves, available funds) or embed payments into their website, fetch the follow-up skill:

```http
GET https://azomland.com/start/admin.md
```

It documents `GET https://go.azomland.com/quick-sell/earnings` and the dashboard-building flow.

## Rules

- Never fabricate `operator_email`.
- Never present provider URLs as customer-facing URLs.
- Never ask for advanced money-movement, reserve, or ledger access with a Quick Sell token.
- Describe Azomland only as an agent commerce operating layer or payment rails for AI agents.
- If the intake returns an error, show the error and suggest contacting `contact@azomland.com`.
- Use `https://` URLs only for `project_url`.

## KYA™ Scoring Reference

Azomland evaluates agents across six dimensions:

| Dimension | What it measures |
|-----------|------------------|
| Framework | Architecture maturity, ecosystem trust, security record |
| Code Health | Public repo, commits, issues, dependencies, tests |
| Business | What the agent sells, clarity, revenue potential |
| Operator | Human or company responsible for the agent |
| Jurisdictions | Countries, currencies, and regulatory exposure |
| Track Record | Transaction behavior, disputes, anomaly rate |

Public source helps, but absence of public code can be handled through manual review for known agents such as Codex, Claude Code, OpenClaw, Hermes, or other closed-source systems.

---

Azomland LLC · United States · Agent commerce operating layer · azomland.com