{
  "company": "Pactum",
  "slug": "pactum",
  "website": "https://pactum.cc",
  "audit_date": "2026-04-10",
  "overall_score": 72,
  "tier": "Emerging",
  "tier_as_published": "E",
  "pillars": {
    "P1": {
      "name": "Signal Architecture",
      "score": 16,
      "max": 25
    },
    "P2": {
      "name": "Clarity Stack",
      "score": 20,
      "max": 25
    },
    "P3": {
      "name": "Trust Envelope",
      "score": 12,
      "max": 20
    },
    "P4": {
      "name": "Velocity Triggers",
      "score": 9,
      "max": 10
    },
    "P5": {
      "name": "Gravity Design",
      "score": 15,
      "max": 20
    }
  },
  "criteria": [
    {
      "id": "P1-A",
      "pillar": "P1",
      "name": "Structured Data",
      "score": 2,
      "max": 5,
      "evidence": "Homepage HTML has minimal schema.org markup; no Offer, Product, or AggregateRating schema detected. Basic Organization markup present but not sufficient for agent parsing."
    },
    {
      "id": "P1-B",
      "pillar": "P1",
      "name": "Machine-Readable Pricing",
      "score": 3,
      "max": 5,
      "evidence": "Fee structure discoverable via page scraping in HTML text; USDC amounts are explicitly stated in prose/tables but not tagged with schema.org/Offer or structured JSON. Parseable but not machine-tagged."
    },
    {
      "id": "P1-C",
      "pillar": "P1",
      "name": "llms.txt / Agent Layer",
      "score": 2,
      "max": 5,
      "evidence": "No /llms.txt found at root. Developer documentation exists and is technically oriented, but not explicitly structured for LLM or agent consumption."
    },
    {
      "id": "P1-D",
      "pillar": "P1",
      "name": "API / MCP Availability",
      "score": 5,
      "max": 5,
      "evidence": "Full REST API with documentation; agent-callable endpoints for discovering, evaluating, and purchasing marketplace services. API-first architecture clearly designed for programmatic consumption."
    },
    {
      "id": "P1-E",
      "pillar": "P1",
      "name": "Discoverability (GEO)",
      "score": 4,
      "max": 5,
      "evidence": "Strong developer-focused content with clear technical narrative. Indexed content explains agent-to-agent commerce well; structured for technical audience retrieval."
    },
    {
      "id": "P2-A",
      "pillar": "P2",
      "name": "Offer Completeness",
      "score": 4,
      "max": 5,
      "evidence": "Marketplace listings include service description, USDC pricing, and API endpoint in a consistent format. Nearly single-source parseable; minor gaps in edge-case coverage."
    },
    {
      "id": "P2-B",
      "pillar": "P2",
      "name": "Scope & Limits",
      "score": 4,
      "max": 5,
      "evidence": "API rate limits documented in developer docs; per-listing service caps stated. Not structured as machine-tagged JSON but clearly present and findable."
    },
    {
      "id": "P2-C",
      "pillar": "P2",
      "name": "Substitution Rules",
      "score": 3,
      "max": 5,
      "evidence": "Some fallback guidance present in FAQ and docs; no explicit, machine-readable substitution protocol for failed or unavailable transactions."
    },
    {
      "id": "P2-D",
      "pillar": "P2",
      "name": "Conditional Logic",
      "score": 4,
      "max": 5,
      "evidence": "Pricing conditions are visible and documented; vendor-specific conditions accessible via listing detail API. Some conditions require parsing multiple pages."
    },
    {
      "id": "P2-E",
      "pillar": "P2",
      "name": "Semantic Precision",
      "score": 5,
      "max": 5,
      "evidence": "Precise technical language throughout; USDC amounts explicitly stated; no vague marketing claims detected (\"best-in-class,\" \"powerful,\" etc.). Definitions consistent across pages."
    },
    {
      "id": "P3-A",
      "pillar": "P3",
      "name": "Verifiable Performance",
      "score": 2,
      "max": 5,
      "evidence": "No uptime SLA, status page, or third-party performance verification found. Self-reported reliability claims only; no G2, Trustpilot, or independent audit data."
    },
    {
      "id": "P3-B",
      "pillar": "P3",
      "name": "Scoped Permissions",
      "score": 3,
      "max": 5,
      "evidence": "API key scoping available with some permission tiers documented. No explicit agent-time-bounded or action-bounded permission scopes found."
    },
    {
      "id": "P3-C",
      "pillar": "P3",
      "name": "Audit Trail",
      "score": 4,
      "max": 5,
      "evidence": "On-chain USDC transaction records provide immutable, verifiable audit trail on Base blockchain. Not human-readable dashboard but blockchain-verifiable for agent systems."
    },
    {
      "id": "P3-D",
      "pillar": "P3",
      "name": "Behavioral Consistency",
      "score": 3,
      "max": 5,
      "evidence": "Marketplace terms versioned; change notification policy referenced in docs. Platform is relatively new; long-term stability track record not yet established."
    },
    {
      "id": "P4-A",
      "pillar": "P4",
      "name": "Friction-Free Activation",
      "score": 5,
      "max": 5,
      "evidence": "Instant API key issuance; no sales call, approval gate, or human review required. Fully self-serve onboarding; agents can activate and transact without human involvement."
    },
    {
      "id": "P4-B",
      "pillar": "P4",
      "name": "Agent Decision Signals",
      "score": 4,
      "max": 5,
      "evidence": "Free trial credits available; marketplace discovery API allows agent to evaluate services before purchase; pricing signals clearly communicated. Missing: explicit \"recommended for agents\" or confidence signals."
    },
    {
      "id": "P5-A",
      "pillar": "P5",
      "name": "Integration Depth",
      "score": 3,
      "max": 5,
      "evidence": "USDC wallet integration and transaction history create moderate switching cost. API integration is meaningful but not deeply proprietary; marketplace data could migrate."
    },
    {
      "id": "P5-B",
      "pillar": "P5",
      "name": "Agent Memory Layer",
      "score": 2,
      "max": 5,
      "evidence": "No persistent agent memory or personalization layer found. Each transaction is independent; no account-level history surfaced via API for agent consumption."
    },
    {
      "id": "P5-C",
      "pillar": "P5",
      "name": "Programmatic Renewal",
      "score": 5,
      "max": 5,
      "evidence": "Subscription and recurring payment endpoints fully documented and agent-callable. Auto-renewal supported natively via API without human gate."
    },
    {
      "id": "P5-D",
      "pillar": "P5",
      "name": "Compounding Value",
      "score": 5,
      "max": 5,
      "evidence": "Network effects compound clearly: more service providers \u2192 more agent buyers \u2192 more providers. 100+ listings create genuine compounding discovery value; marketplace grows more valuable as agents transact."
    }
  ],
  "strongest_signals": [
    {
      "title": "API-first architecture (P1-D: 5/5)",
      "detail": "Every core action \u2014 discovery, evaluation, purchase \u2014 is API-callable without human involvement. This is the gold standard for agent-native velocity."
    },
    {
      "title": "Semantic precision (P2-E: 5/5)",
      "detail": "USDC pricing is explicit, terms are precise, and there are no vague marketing claims. Agents can parse Pactum's offers without ambiguity."
    },
    {
      "title": "On-chain audit trail (P3-C: 4/5)",
      "detail": "Blockchain settlement provides an immutable, agent-verifiable transaction record \u2014 a rare trust signal in early agent infrastructure."
    },
    {
      "title": "Network effects (P5-D: 5/5)",
      "detail": "The marketplace compounding model is genuine; value increases with each new provider and buyer agent."
    }
  ],
  "critical_gaps": [
    {
      "title": "No schema.org markup (P1-A: 2/5)",
      "detail": "Agents relying on structured data signals will find nothing machine-tagged on Pactum's pages. This blocks discovery via AI retrieval systems."
    },
    {
      "title": "No /llms.txt (P1-C: 2/5)",
      "detail": "No agent identity document exists. Agents have no standardized way to understand what Pactum is, what it offers, and how to interact with it programmatically."
    },
    {
      "title": "No verifiable performance data (P3-A: 2/5)",
      "detail": "Zero uptime SLA, no status page, no third-party reliability verification. For autonomous agents making purchasing decisions, this is a significant trust gap."
    },
    {
      "title": "No agent memory layer (P5-B: 2/5)",
      "detail": "Each interaction starts from scratch. Agents cannot build on prior transaction history, preferences, or usage patterns \u2014 limiting the depth of agent loyalty."
    }
  ],
  "priority_actions": [
    {
      "action": "Publish /llms.txt",
      "points_gain": 5,
      "pillar": "P1",
      "effort": "Low"
    },
    {
      "action": "Add schema.org/Offer markup to marketplace listings",
      "points_gain": 4,
      "pillar": "P1",
      "effort": "Low"
    },
    {
      "action": "Publish a public status page with uptime SLA",
      "points_gain": 4,
      "pillar": "P3",
      "effort": "Low"
    },
    {
      "action": "Build an agent memory / account history API",
      "points_gain": 5,
      "pillar": "P5",
      "effort": "Med"
    },
    {
      "action": "Document explicit substitution and fallback rules",
      "points_gain": 3,
      "pillar": "P2",
      "effort": "Low"
    }
  ],
  "executive_summary": "Pactum sits solidly in the **Emerging** tier (72/100) \u2014 the highest-scoring company audited to date \u2014 thanks to an API-first architecture that genuinely enables agent-to-agent commerce, clean semantic precision in its offer language, and real on-chain trust signals. Its strongest pillar is Velocity (9/10): an agent can discover, evaluate, and purchase with zero human involvement, which is the correct design for agent-native infrastructure. The critical gap is Signal Architecture: despite being purpose-built for AI agents, Pactum has no schema.org markup and no /llms.txt \u2014 making it invisible to agents who discover services via AI retrieval systems rather than direct API calls. Publishing /llms.txt and adding Offer schema markup are two low-effort actions that could push Pactum into Agent-Ready territory (85+) within days.",
  "rubric_version": "v1-2026-04 (20 criteria, 100 raw points; P3-E Agent Registration added to rubric v2 in 2026-06, not scored in this audit)",
  "framework": "Agent Native Offers \u2014 The Agent Sale framework",
  "source_file": "2026-04-10 \u2014 Pactum \u2014 Agent Native Offer Audit.md",
  "rank": 2
}