startups as

Optometry.Claims optometry.claims

namespace seednamespace

One.claims vertical instance: the vision claim as a typed record an agent can file, on the.claims document grammar.

From the Startup card at api.sb/optometry.claims · Designed · Service, Agent, Dataset.

contested · 1 tension

tier: namespace · projection lens A reads namespace (namespace); lens B reads projection (brand)

The two lenses (and any ledger statement) are kept side by side, not resolved. Most names carry one; it is a reading to explore, not an error.

What it is

Tier	namespace	Inferred · med · portfolio-lens-a.tsv (tier)
Status	namespace seed	Inferred · med · lens A tier namespace
Product kind	—	no provenance
Core noun	—	no provenance
Buyer and position	Deliverable Mint: "optometry"	Inferred · low · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	S20 [noun].claims typed claim schemas	Inferred · med · portfolio-lens-a.tsv (set_or_journey)
Abstraction	V-health	Inferred · low · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · low · portfolio-lens-b.tsv (role)
Registrar	porkbun	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Optometry.Claims

                            Optometry.Claims                                         centre
                                    │
                               API.Insure                                            the businesses
                      ╱                           ╲
   APIs.Credit                                             Gigs.Claims               brands
        │             ╲             ╲
  Searches.Dev                 Gigs.Loans                 MongoLake.Dev              the abstractions
                                    │
                              APIs.Finance                                           the businesses
                                    │
                               Headless.ly                                           the abstractions

Click any node to re-centre the stack on it; the trail above keeps the nesting. Each node's own page is one more click.

Neighbours

Same abstraction (V-health)

Gigs.Care Gigs.Clinic Gigs.Dentist Gigs.Doctor Gigs.Health Gigs.Healthcare Gigs.Hospital Genes.org.ai Health.org.ai HL7.org.ai Med.org.ai Molecules.org.ai Safety.org.ai Species.org.ai Aides.Care Appointments.Care Bench.Clinic Chartnotes.co Copays.Claims Denials.Services Denied.Click Discharge.Click Edi834.Dev Emrcheck.Dev Hospicecap.Dev Intake.Clinic Openenrollment.Click Perdiem.Health Pharmtechs.Work Precerts.co Priorauth.Click Priorauths.co Rails.Health Recalls.Clinic Records.Clinic Rxverify.Dev Scribing.Services Shifts.Care Shifts.Health Shingle.Clinic +5 more

Listed by

no discovery view lists it yet

In logo rows

API.Insure's row buildable

Slices

in no slice

Relationships (1)

from	verb	to	provenance
Optometry.Claims	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	API.Insure	Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def optometry.claims: built on apis.claims [low] — The fan-out places it on apis.claims, the .claims family's rail (batch b020 writes it).

Edit log

loading the versions of this record from api.sb…

Machine-readable: /optometry.claims.json