All 20 Criteria
P1-A Structured Data — 3/5
FAQPage (13 Q&A items) and SoftwareApplication schema confirmed on homepage. Does not include Product/Offer/AggregateRating schema that agents need to evaluate commercial offers directly.
P1-B Machine-Readable Pricing — 2/5
Pricing is clearly displayed in an HTML table with four tiers ($249/$499/$1,499/Enterprise), credit costs, SKU limits, and workspace counts. However, no schema.org/Offer markup or JSON pricing spec detected. An AI agent must parse prose/HTML, not a structured feed.
P1-C llms.txt / Agent Layer — 0/5
Fetching /llms.txt returned a 404. No agent identity layer or LLM-consumption file is present, despite the company's core product being about AI discoverability.
P1-D API / MCP Availability — 2/5
"Headless systems + API" is listed as a feature for Growth ($499/mo) and higher plans. No public API documentation URL, OpenAPI spec, or MCP server was found during research. API access appears to exist but is not agent-discoverable.
P1-E Discoverability (GEO) — 4/5
Ironic but positive: Wildcard's entire product is Generative Engine Optimization, so their own content is well-structured, schema-tagged, and optimized for AI retrieval. They appear in AI shopping searches and have strong structured content. Minor gap: no llms.txt to self-describe for agent context windows.
P2-A Offer Completeness — 4/5
Pricing page clearly defines what's included at each tier: credit quantities, SKU limits, workspace count, automation count, support tier. Competitive by category standards. Minor gap: some features (e.g., "custom integrations") lack specificity.
P2-B Scope & Limits — 4/5
Credit costs per action explicitly listed (blog posts = 100 credits, quick wins = 50 credits), SKU caps per tier stated, workspace and automation maximums documented. Rate limits for the API are not published.
P2-C Substitution & Fallback Rules — 1/5
No guidance on service unavailability, what happens if credit runs out mid-workflow, or fallback behavior for tracking failures. An AI agent operating on behalf of a brand would have no guidance on contingency.
P2-D Conditional Logic Transparency — 2/5
Enterprise pricing requires contacting sales with no disclosure of what triggers enterprise eligibility. ACP integration terms are not machine-readable. Conditions scattered across FAQs and product pages.
P2-E Semantic Precision — 3/5
Mix of precise and vague. Specific: credit costs per action, SKU limits, workspace counts, credit-to-action ratios (~1 credit = 0.01 action). Vague: "leading GEO platform," "AI visibility," "win ChatGPT Shopping" — terms not formally defined for agent evaluation.
P3-A Verifiable Performance Data — 1/5
No public status page found. No G2, Trustpilot, or third-party verified reviews found for this specific product (GEO platform launched 2025). Claims of effectiveness are present on homepage but entirely self-reported from a seed-stage company.
P3-B Scoped Permission Model — 2/5
Access is scoped by workspace and user tier, but there are no agent-specific permission boundaries (time-limited, action-bounded, or spend-capped agent scopes). A human workspace model, not an agent permission model.
P3-C Audit Trail / Transaction Log — 1/5
No evidence of machine-accessible audit logs. Dashboard analytics exist for human review of product performance, but no programmatic audit trail for agent transactions or credit consumption.
P3-D Behavioral Consistency Signals — 1/5
Seed-stage company (founded 2025, $500K raised per Tracxn). No versioned terms of service, no published change log, no stated notice periods for pricing or API changes. Stability track record is too new to evaluate.
P4-A Friction-Free Activation — 3/5
Self-serve signup exists (credit card required for paid plans). "AI Visibility Audits" offered free. However, no API key instant issuance for Growth-tier API access confirmed — onboarding flow requires account creation and plan selection before API access.
P4-B Agent Decision Signals — 3/5
Free entry point (free audit) provides a programmatic taste of value. Credit-to-action mapping published (e.g., 100 credits = 1 blog post). However, no explicit agent-legible "try before commit" signal or programmatic evaluation path for autonomous decision-making.
P5-A Integration Depth / Switching Cost — 3/5
Shopify integration creates moderate switching cost via synced SKU data and tracked product history. Enterprise PIM connect and headless CMS integrations deepen lock-in. Not extreme — a brand could export data and rebuild elsewhere within weeks.
P5-B Agent Memory / Personalization Layer — 2/5
Platform accumulates product performance data over time (which prompts surface which SKUs), but this history is not accessible via agent-readable API. No documented memory endpoint or context layer for agents to query historical performance.
P5-C Programmatic Renewal Signals — 1/5
Standard monthly/annual SaaS subscription. No agent-accessible renewal API, no programmatic re-up signal. Renewals happen through a human billing flow.
P5-D Compounding Value Signal — 3/5
The platform's value genuinely compounds: as more prompts are tracked and competitors are benchmarked, the data becomes richer and the recommendations more precise. However, this compounding value is not surfaced in an agent-readable format. An agent evaluating "is this still worth renewing?" has no signal to query.
Rubric v1 (April 2026). Scores reflect the company's state on the audit date and may have improved since.