Investor Relations

Company snapshot

01

Product

FacetThe face a business turns toward machines

Entity

Facet, LLCCalifornia LLC

Coverage

HorizontalAll businesses with a web, map, or social presence

The thesis, in one paragraph

02

Scraping is breaking, and the protocol rails that replace it: MCP, KYAPay, x402, RFC 9421, all standardized inside the same 30-month window. Each solves exactly one layer of the problem. None of them composes with the others on its own. Facet is the product layer that bundles them. One install gives a website cryptographic identity, per-query metering, signed receipts, and a shared audit trail. We monetize the four points every agent-to-business interaction has to flow through anyway: discover, identify, transact, and audit.

Our reference go-to-market wedge is food-and-beverage supply chains, regulated, audit-heavy commerce where signed receipts, lot-level provenance, and per-query metering are things buyers and sellers already need to transact at all. Once the substrate is mounted there, the same primitives extend horizontally to every other vertical an agent queries, which, over the planning horizon, is all of them.

Proof

03

On 10 June 2026, in the first Agent-to-Business (A2B) commerce transaction on x402B, an autonomous AI agent completed an end-to-end purchase from the real LARUCE Beauty Shopify store. It proved its identity, checked out, and the payment settled over x402B, Boson Protocol's escrow exchange mechanism, on Base mainnet. Funds were held in escrow until the order was fulfilled. Boson Protocol names Facet a launch partner for x402B.

Live

Real agent, real storeAutonomous checkout and settlement at LARUCE on Shopify

Settled

x402B on BaseEscrow-backed, released on fulfillment

Partner

Boson Protocolx402B launch partner

Inspectable

Open-source SDKThe open-source escrow adapter behind it, github.com/facet-llc/sdk

Read the writeup on the Devlog, inspect the integration in the open-source SDK, and request the narrated demo in the data room below.

Why we believe it's defensible

04

Standards · not silos

Facet implements public protocols (MCP, KYAPay, x402, RFC 9421) rather than a proprietary network. The moat is the operator-of-record relationship, the per-tenant audit log, and the schema-generation layer, none of which any of those specifications cover.

Compliance-positive

Facet's append-only, signed audit log is structurally the artifact regulators ask for in any audit-heavy industry: finance, healthcare, supply chain, marketplaces. Mount events double as compliance events, without category-specific custom work.

Audit-first GTM

The adoption funnel opens with a free Agent Traffic Audit, a classified report built from the site's own logs that makes invisible agent traffic visible. The operator mounts the Terminal to monetize the same traffic the audit classified. The conversion path runs entirely on data the prospect already owns.

Settlement neutrality

Facet routes payments over USDC on Base and traditional card rails interchangeably. Buyers don't have to adopt crypto; sellers don't have to refuse it. Both rails produce the same CaptureOk { settlement_id, settled_at } receipt envelope. SDK consumers write rail-agnostic code. The reference adapters ship on npm (@facet-llc/payment-adapter-x402-coinbase, @facet-llc/payment-adapter-stripe).

Auditability by default

Every read, transaction, and licensing event lands on an append-only, signed audit trail. That is a regulatory, legal, and forensic asset scrapers structurally cannot produce.

Open verifier kit

KYAPay is a multi-issuer identity standard. Any compliant issuer can mint tokens Facet verifies. @facet/kya-verifier ships open-source so any buyer can verify Facet-signed artifacts outside the platform. Adoption of the verifier widens the network without locking buyers in, a flywheel, not a moat-by-imprisonment.

Developer resources

05

The contract is the receipt

Facet's full HTTP surface is a published OpenAPI 3.1 specification, generated from the protocol's TypeScript types and CI-enforced against the live handler. Drift between the spec and the runtime is a build-system failure, not a code-review opinion. Investors and partners doing technical diligence can verify every claim below against the live URLs, today, without scheduling a call.

View OpenAPI spec ↗ agents.txt v1.2 manifest ↗

Canonical contract

terminal.facet.llc/v1/openapi.json, 70 routes, OpenAPI 3.1, generated from @facet-llc/adapter TypeScript types. Two CI gates enforce: spec-drift-check + spec-emit-idempotency.

Per-endpoint security

69 of 69 non-deprecated routes carry an x-facet-security metadata block (auth mode, tenant scope, rate-limit, idempotency, side effects, egress, audit trail, failure modes, response signing). A human-readable checklist auto-generates from the spec. Security reviewers grep, they don't ask for a call.

Spec-generated SDKs

@facet-llc/sdk-node, @facet-llc/sdk-deno, @facet-llc/sdk-python, all regenerate from the canonical spec via scripts/regenerate-sdks.sh. Marginal cost of a Java / Go / Rust SDK is one CI job, not one engineer-week.

Multi-rail payment acceptance (npm, 2026-05-26)

Six @facet-llc/* packages published as a coordinated release. The protocol exports FacetPaymentRailAdapter with a rail-symmetric CaptureOk { settlement_id, settled_at } envelope; two reference adapters ship (@facet-llc/payment-adapter-x402-coinbase, @facet-llc/payment-adapter-stripe); two reference origination verifiers ship (@facet-llc/origination-aws-agentcore, @facet-llc/origination-coinbase-cdp). Self-hosters npm install the entire receive-side stack. Public mirror: facet-llc/sdk ↗.

Per-merchant overlays

Any external operator runs Facet at their own domain via a small declarative overlay file (OpenAPI Overlay Specification 1.0.0). Facet's own deployment at terminal.facet.llc is dogfood merchant #1. checkInvariants guarantees no overlay can strip a protected endpoint.

Security posture

The protocol, OpenAPI contract, and SDKs are open source and independently inspectable at github.com/facet-llc. API responses carry a cryptographic provenance signature, and the managed-wallet model is structurally non-custodial. No merchant signing authority ever resides on Facet infrastructure.

Source

Public protocol repo: github.com/facet-llc/spec. Reference implementation (private monorepo) available to qualified investors under the data-room NDA.

How investors engage

06

Request the data room

For qualified institutional and accredited investors. Send a brief intro and we'll route to the right person on our side, then share access to the data room (deck, financials, security pack, customer references) under a standard NDA.

Use the contact form, set Reason → Investor, and include your firm + the fund / mandate the introduction is for. Replies typically within one to two business days.

Request data room → Read the public thesis

Press & analysts

Use the contact form with reason Press & research. We respond on background and on-the-record requests.

Existing investors

Quarterly updates land in your inbox from the address on the cap-table record. For ad-hoc questions, reach out via the channel you were onboarded on.

Standards & integrations

Builders working on MCP, RFC 9421, KYAPay, or x402, use reason Partnership. We co-design where it benefits the protocol layer.

Recruiting

We're hiring across protocol, infra, and GTM. Mention the role in your message; specific listings are linked from the press kit.

Forward-looking statements. This page is corporate communications. It is not an offer to sell, or a solicitation of an offer to buy, any securities. Statements about strategy, market opportunity, regulatory timelines, product roadmap, and projected outcomes are forward-looking and subject to risks and uncertainties; actual results may differ materially. Securities are offered, if at all, only to accredited or qualified investors under available exemptions and pursuant to definitive transaction documents. Nothing here constitutes investment, legal, tax, or accounting advice.

Building the substrate the agent web settles on.