Metiora logo Metiora
GitHub API
Home Docs Blog GitHub Services API
Documentation

Metiora product documentation

This guide explains what Metiora is, how buyers purchase packages on the OKX.AI marketplace, and how the live service is structured in production.

Version 1.0.9 Live base: agentmetiora.xyz ASP agent #6860

1. Introduction

Metiora is an AI operating partner for founders, delivered as an Agent Service Provider on the OKX.AI marketplace. The service keeps structured founder and startup memory, then generates practical packages such as blueprints, investor materials, grant applications, partnership outreach, token planning, and health reviews.

Buyers interact through public HTTPS endpoints. Product calls are gated by x402 payment on X Layer. Operators manage private routes with a Metiora API key. The public website, documentation, blog, and API all run on https://agentmetiora.xyz.

Packages are returned as structured JSON and Markdown so agents and humans can both consume the output. Generation is designed to finish within marketplace time windows and to return clear JSON errors instead of hanging connections.

2. Who this is for

Marketplace buyers

Agents and users purchasing founder packages through OKX.AI. You do not need the Metiora operator API key. You pay with x402 and either send founder+startup on the paid call (auto-bootstrap) or reuse profile UUIDs from free bootstrap, then receive dual JSON and Markdown deliverables.

ASP operators

People running this deployment. You hold production secrets, monitor health, and may use authenticated admin routes for memory and internal tooling.

Integrators

Developers wiring Metiora into agent workflows. Use the services catalog as the source of truth for URLs, prices, and required body fields.

3. Services

Metiora currently lists six paid products. Prices are in USDT0 on X Layer mainnet. Each product needs founder and startup context: either inline objects on the paid call or profile UUIDs. An optional blueprint ID may be provided when a package should reference a prior blueprint.

Startup Blueprint · $3 USDT0

POST /v1/a2mcp/startup-blueprint
Produces a strategic startup blueprint from company memory. Useful when founders need a clear, shareable plan in dual JSON and Markdown form.

Investor Ready Package · $3 USDT0

POST /v1/a2mcp/investor-ready
Builds investor facing materials with readiness scoring and memo style narrative for fundraising conversations.

Grant Builder Package · $2 USDT0

POST /v1/a2mcp/grant-builder
Creates grant oriented content with impact narrative and application structure for program and fund applications.

Partnership Studio · $1 USDT0

POST /v1/a2mcp/partnership-studio
Generates partnership outreach materials covering fit and mutual value for alliance discussions.

Token Launch Kit · $0.3 USDT0

POST /v1/a2mcp/token-launch-kit
Token strategy package: utility, distribution outline, and planning notes grounded in your inputs. This is not a contract deploy, mint, or on-chain launch tool.

Startup Health Review · $0.3 USDT0

POST /v1/a2mcp/startup-health
Runs a multi dimension health assessment with scores and priority actions for execution tracking.

The live catalog at /v1/a2mcp/services always reflects production prices, endpoints, payTo, and body modes. Marketplace registration should copy those values exactly. When packageLlm.enabled is true, paid packages keep dual JSON and Markdown but enrich narratives with a live model grounded only in founder and startup memory (deterministic generator if the model is unavailable). Outputs are personalized from the buyer’s inputs — not a fixed brand template. With only the minimum required fields (founder email + name, startup name + industry), generators still produce company-specific content — including a token name/symbol derived from the startup name (never a Metiora “METI” default). Optional fields such as problemStatement and productDescription improve depth; they are not required to avoid a generic package. Allocation and budget percentages are real numbers that sum to 100%. On every paid call, founder/startup fields in the request body override any stored profile for that generation and are written back so memory stays in sync. generation.mode is deterministic or llm — never a silent brand template.

4. Buyer guide

Follow this sequence for a complete purchase path. Marketplace buyers usually use the inline path so a single paid call both creates memory and generates the package.

Step 1 · Choose a product

Read the services catalog for full URLs, prices, fee token, payTo, and body modes. Do not invent paths. Only listable products appear in the catalog.

Step 2 · Provide founder and startup context

Mode A · Inline (recommended for first-time / marketplace buyers)

Send founder and startup objects on the paid product POST. After payment verifies, Metiora creates profiles automatically. Minimum fields work; recommended fields produce better personalization. 

POST https://agentmetiora.xyz/v1/a2mcp/startup-blueprint
Content-Type: application/json

{
  "founder": {
    "email": "founder@example.com",
    "fullName": "Ada Founder"
  },
  "startup": {
    "name": "Acme Labs",
    "industry": "AI",
    "problemStatement": "…",
    "productDescription": "…",
    "uniqueValueProp": "…",
    "targetAudience": "…",
    "businessModel": "…",
    "stage": "seed",
    "tractionSummary": "…"
  }
}

Required founder fields: email, fullName. Required startup fields: name, industry. Recommended: problemStatement, productDescription, uniqueValueProp, targetAudience, businessModel, revenueModel, stage, tractionSummary, competitors, geographicMarkets, fundraisingGoal, and for token work: tokenUtility, tokenUseCase, targetBlockchain, tokenSupplyNotes, tokenDistributionNotes, regulatoryJurisdiction.

Mode B · Profile IDs (returning buyers or multi-package sessions)

Call free bootstrap once per founder and startup pair, then reuse the UUIDs on paid routes. 

POST https://agentmetiora.xyz/v1/a2mcp/bootstrap
Content-Type: application/json

{
  "founder": {
    "email": "founder@example.com",
    "fullName": "Ada Founder"
  },
  "startup": {
    "name": "Acme Labs",
    "industry": "AI"
  }
}

The response includes founderProfileId and startupProfileId. If the email already exists, the founder is reused and a new startup is attached to that founder.

Step 3 · Pay and execute

POST the product endpoint with either body mode. Without a valid payment header, the API returns HTTP 402 with payment requirements. Complete the x402 payment using the OKX agent wallet flow, then replay the request with payment headers. On success you receive the package payload. Auto-bootstrap (inline mode) runs only after payment is verified.

Step 4 · Use the deliverable

Responses include structured content and Markdown grounded in the memory you provided. If company memory is sparse, Metiora still returns a package and may include a readiness notice so the buyer is not blocked after paying. Enrich recommended fields on the next call for stronger output.

5. API reference

Public discovery

  • GET /health · service health and payment capability
  • GET /v1/a2mcp/services · catalog of listable products
  • POST /v1/a2mcp/tools · operations list for agent tooling
  • POST /v1/a2mcp/bootstrap · create founder and startup IDs
  • GET /avatar.png · marketplace avatar asset

Paid product methods

All of the following are POST and require x402 payment for delivery:

  • /v1/a2mcp/startup-blueprint
  • /v1/a2mcp/investor-ready
  • /v1/a2mcp/grant-builder
  • /v1/a2mcp/partnership-studio
  • /v1/a2mcp/token-launch-kit
  • /v1/a2mcp/startup-health

Request body (two modes)

Inline auto-bootstrap (marketplace first purchase):

{
  "founder": { "email": "…", "fullName": "…" },
  "startup": { "name": "…", "industry": "…", "problemStatement": "…" },
  "blueprintId": "uuid"
}

Profile IDs (after bootstrap or a prior paid call):

{
  "founderProfileId": "uuid",
  "startupProfileId": "uuid",
  "blueprintId": "uuid"
}

blueprintId is optional. When using profile IDs, the startup must belong to the founder. Cross profile requests are rejected. Catalog field requiredBodyFields is published as founderProfileId|founder and startupProfileId|startup.

6. Payments

Metiora uses the OKX x402 exact scheme on X Layer mainnet. Unpaid product calls return payment required responses that describe the network, amount, and receiving address for that deployment.

  • Network: eip155:196 (X Layer mainnet)
  • Fee token: USDT0 at 0x779ded0c9e1022225f8e0630b35a9b54be713736
  • Seller payTo: 0xd4a80cdda4d12896ea3af9d210477c014758aa9d (also in live catalog)
  • Scheme: x402 exact

Marketplace listings must use the same fee token, payTo, amounts, and full HTTPS product URLs returned by the live catalog. Token mismatches and unreachable endpoints are common reasons for review failure.

7. Operators

Production requires environment configuration for the database, operator API key, OKX facilitator credentials, and payTo wallet. These values belong in host secrets, never in the public git repository.

Private routes accept either header form: 

x-api-key: YOUR_KEY

Authorization: Bearer YOUR_KEY

Local development uses .env copied from .env.example. See the GitHub repository README for install commands and the project map.

8. Marketplace listing

Metiora is registered as ASP agent #6860. When preparing or updating a listing:

  • Public listing: https://www.okx.ai/agents/6860
  • Use avatar https://agentmetiora.xyz/avatar.png
  • Register only the six product endpoints on agentmetiora.xyz
  • Match catalog prices exactly
  • Confirm unpaid POSTs return 402, not 404 or timeout
  • Publish required body fields (profile IDs or founder+startup) in listing metadata
  • Keep the deployment online during review
  • Category for this ASP is software services for founder tooling, not a finance product

9. Security model

Metiora separates public marketplace access from private operator access.

  • Public: website, health, avatar, catalog, free bootstrap, paid A2MCP products (inline auto-bootstrap only after payment verifies)
  • Private: memory administration and internal helpers behind the API key

Do not commit .env, local key dumps, facilitator secrets, or wallet private keys. The public repository ignores those paths by default. If a secret is exposed, rotate it immediately.