# lo.st

> Quietly reunite lost things with the people who love them. Public lost & found feed plus enterprise lost & found infrastructure for airports, transit, hotels, venues, and campuses.

## Hubs

- [Solutions](https://lo.st/solutions)
- [Resources](https://lo.st/resources)
- [At Scale](https://lo.st/at-scale)
- [API](https://lo.st/api)

## Solutions

- [Aviation](https://lo.st/solutions/aviation): Lost & found for airlines, airports, and ground handlers.
- [Hotels](https://lo.st/solutions/hotels): Hospitality lost & found across front desk, housekeeping, F&B.
- [Transit](https://lo.st/solutions/transit): Rail, bus, ferry and ride-share lost & found.
- [Venues & stadiums](https://lo.st/solutions/venues): High-volume event lost & found with gate-time SLAs.
- [Universities & schools](https://lo.st/solutions/campuses): Campus lost & found across residences, libraries, sports.
- [Retail & malls](https://lo.st/solutions/retail): Multi-store lost & found with central reconciliation.
- [Coworking & offices](https://lo.st/solutions/coworking): Member-friendly lost & found for shared workspaces.
- [Healthcare](https://lo.st/solutions/healthcare): Patient-property handling with chain-of-custody.
- [Property management](https://lo.st/solutions/property): Resident lost & found across portfolios.
- [Events & festivals](https://lo.st/solutions/events): Pop-up lost & found that scales for the weekend and disappears Monday.
- [Intake from anywhere](https://lo.st/solutions/use-cases/intake-from-anywhere)
- [Instant match](https://lo.st/solutions/use-cases/instant-match)
- [Claim verification](https://lo.st/solutions/use-cases/claim-verification)
- [Shipping and pickup](https://lo.st/solutions/use-cases/shipping-and-pickup)
- [Disposition and donations](https://lo.st/solutions/use-cases/disposition-and-donations)
- [Chain of custody](https://lo.st/solutions/use-cases/chain-of-custody)
- [Public lost-property portal](https://lo.st/solutions/use-cases/lost-property-portal)
- [Staff mobile app](https://lo.st/solutions/use-cases/staff-mobile)
- [Guest self-service](https://lo.st/solutions/use-cases/guest-self-service)
- [Evidence and audit](https://lo.st/solutions/use-cases/evidence-and-audit)
- [AI description match](https://lo.st/solutions/use-cases/ai-description-match)

### Solutions — published articles

- [Lost & found for aviation](https://lo.st/solutions/aviation): Run aviation lost & found across cabin, terminal, and ground ops without the spreadsheet. IATA 753 aware, multi-station ready.
- [Instant match](https://lo.st/solutions/use-cases/instant-match): Match claims to found items the moment either is logged. Image similarity + description embeddings + location and time bounds.
- [Lost & found for hotels](https://lo.st/solutions/hotels): Run hotel lost & found across front desk, housekeeping, and F&B without spreadsheets. Guest portal, instant match, shipping in one workflow.

## Resources

- [Blog](https://lo.st/resources/blog): Field notes from operators.
- [Field guide (PDF)](https://lo.st/resources/field-guide): Operator playbook, gated download.
- [Glossary](https://lo.st/resources/glossary): Plain-language definitions for L&F terms.
- [Integration directory](https://lo.st/resources/integrations): Pre-built connectors for OPERA, SAP, ServiceNow, etc.
- [Webinars](https://lo.st/resources/webinars): Live and on-demand sessions.
- [Newsletter](https://lo.st/resources/newsletter): Monthly digest for L&F managers.
- [Compliance hub](https://lo.st/resources/compliance): SOC 2, ISO 27001, GDPR, CCPA, DPA.
- [Help center](https://lo.st/resources/help): Product help for end users and staff.

### Resources — published articles

- [Hartsfield-Jackson Atlanta (ATL) lost and found: how to get your stuff back](https://lo.st/resources/guides/atl-airport-lost-and-found): Lost something at Atlanta Airport (ATL)? Here's where to file, who actually holds your item — airport vs. airline vs. TSA — and how to widen the search with lo.st.
- [Compliance hub](https://lo.st/resources/compliance): SOC 2, GDPR, sub-processors, DPA and breach-notification policy for lo.st. The links procurement actually asks for.
- [Integration directory](https://lo.st/resources/integrations): PMS, identity, carrier, locker and ERP integrations available through lo.st — what's shipped, what's in beta, and what we'll build on request.
- [Lost & found glossary](https://lo.st/resources/glossary): Plain-language definitions for the acronyms operators trip over: AHL, OHD, BIR, IATA 753, chain of custody, and more.
- [The 90-second handoff](https://lo.st/resources/blog/the-90-second-handoff): The single biggest variable in lost & found return rates isn't matching — it's the handoff between the finder and the system. Here's how to shrink it.
- [Why we built modern lost & found infrastructure](https://lo.st/resources/blog/modern-lost-and-found-infrastructure): Legacy lost & found vendors take a margin on every shipment. We don't. Here's how that one decision shaped every product surface.
- [Why we stopped counting tickets](https://lo.st/resources/blog/why-we-stopped-counting-tickets): Ticket volume is a vanity metric for lost & found teams. Here's what we replaced it with — and why our customers' boards finally cared.
- [API-first from day one](https://lo.st/resources/blog/api-first-from-day-one): Every screen in lo.st is a documented API call. Here's what that means for your team — and why we won't budge on it.
- [Writing a lost-property policy that actually gets used](https://lo.st/resources/guides/writing-a-lost-property-policy): A practical template for a lost-property policy that staff will read, guests will trust, and lawyers will sign off on.

## At Scale

- [Volume](https://lo.st/at-scale/volume): What 'high volume' actually means at lo.st.
- [Security](https://lo.st/at-scale/security): Controls, certifications, and posture.
- [SAML SSO](https://lo.st/at-scale/saml): Enterprise sign-in with SAML.
- [SCIM provisioning](https://lo.st/at-scale/scim): Automated user lifecycle.
- [Data residency](https://lo.st/at-scale/data-residency): Region pinning for EU, US, and beyond.
- [Disaster recovery](https://lo.st/at-scale/disaster-recovery): RPO, RTO, runbooks.
- [Service-level agreement](https://lo.st/at-scale/sla): Uptime targets and credits.
- [Audit trail](https://lo.st/at-scale/audit): Immutable activity log.
- [Evidence locker](https://lo.st/at-scale/evidence): Chain-of-custody for high-value items.
- [Procurement](https://lo.st/at-scale/procurement): Vendor info, security questionnaires, MSAs.
- [Trust portal](https://lo.st/at-scale/trust): Real-time status, subprocessors, posture docs.
- [Contact sales](https://lo.st/at-scale/contact-sales): Talk to a human.

### At Scale — published articles

- [Running lost & found across a portfolio](https://lo.st/at-scale/multi-property): How to roll lost & found across a portfolio of properties without losing local autonomy or central visibility.

## API

- [Quickstart](https://lo.st/api/quickstart)
- [API reference](https://lo.st/api/reference)
- [Authentication](https://lo.st/api/authentication)
- [Idempotency](https://lo.st/api/idempotency)
- [Webhooks](https://lo.st/api/webhooks)
- [Pagination](https://lo.st/api/pagination)
- [Errors](https://lo.st/api/errors)
- [Rate limits](https://lo.st/api/rate-limits)
- [SDKs](https://lo.st/api/sdks)
- [MCP server](https://lo.st/api/mcp)
- [Subscribe to the Feed](https://lo.st/api/feed-subscribe)
- [Changelog](https://lo.st/api/changelog)

### API — published articles

- [Brand partners](https://lo.st/api/brand-partners): How luggage makers, airlines, hotels, schools, electronics manufacturers, and insurers integrate their product catalog, QR tags, and customer apps with lo.st.
- [Current API model](https://lo.st/api/current-model): Inventory of every existing /api/v1 surface — auth, objects, claims, tags, webhooks, events, audit — and the compatibility promises that govern changes to them.
- [Deep links](https://lo.st/api/deep-links): Canonical lo.st URL shapes, Universal Links + App Links setup, post-login intent preservation, and partner attribution.
- [Android quickstart](https://lo.st/api/mobile-apps/android): Google sign-in via Chrome Custom Tabs, Kotlin coroutines client, CameraX + ML Kit QR scan, and verified App Links against /api/v1.
- [Android · Get started](https://lo.st/api/mobile-apps/get-started-android): A 7-step Android path: pick the right token, sign in via Custom Tabs, create your first object, file your first claim, scan your first tag, verify everything.
- [iOS · Get started](https://lo.st/api/mobile-apps/get-started-ios): A 7-step iOS path: pick the right token, sign in, create your first object, file your first claim, scan your first tag, and verify it all worked.
- [iOS quickstart](https://lo.st/api/mobile-apps/ios): Sign in with Apple, create your first object, scan a QR tag, and handle Universal Links from Swift — using /api/v1 and the lovable.dev OAuth bridge.
- [React Native quickstart](https://lo.st/api/mobile-apps/react-native): Expo SDK 51 and bare RN recipes — auth, QR scan, deep links, push, and /api/v1 from a single shared TypeScript client.
- [Android sample app walkthrough](https://lo.st/api/mobile-apps/sample-app/android): Build the five-screen Android reference app end to end: sign in, list objects, scan QR, register and look up a serial, and receive HMAC-verified webhooks.
- [iOS sample app walkthrough](https://lo.st/api/mobile-apps/sample-app/ios): Build the five-screen iOS reference app end to end: sign in, list objects, scan QR, register and look up a serial, and receive HMAC-verified webhooks.
- [Sample mobile app](https://lo.st/api/mobile-apps/sample-app): Five-screen reference app — sign in, list objects, scan QR, register/look up a serial, and receive HMAC-verified webhooks — with runnable walkthroughs for iOS and Android.
- [Mobile apps](https://lo.st/api/mobile-apps): How native iOS, Android, and React Native apps authenticate against /api/v1, create and update objects, open claims, subscribe to events, and handle QR + deep-link returns.
- [API changelog](https://lo.st/api/changelog): Every change to the lo.st API, dated, with migration notes when breaking.
- [Subscribe to the Feed](https://lo.st/api/feed-subscribe): Three ways to keep up with newly reported lost and found items: an RSS feed, a JSON Feed, or a real-time webhook.
- [MCP server](https://lo.st/api/mcp): lo.st exposes a Model Context Protocol server so AI agents can investigate, summarise, and operate on your data with the same auth and scopes as the REST API.
- [Rate limits](https://lo.st/api/rate-limits): Current rate-limit posture for the lo.st API and recommended client behaviour.
- [Authentication](https://lo.st/api/authentication): Token types, scopes and rotation for the lo.st API. Bearer tokens, per-account isolation, and how to rotate without downtime.
- [Errors](https://lo.st/api/errors): RFC 9457 problem responses for the lo.st API. Stable type URIs, machine-readable, with the catalogue you can ship against.
- [Idempotency](https://lo.st/api/idempotency): How the Idempotency-Key header works in lo.st: 24-hour replay window, scope rules, and the 409 you get when payloads disagree.
- [Pagination](https://lo.st/api/pagination): Opaque cursor pagination for the lo.st API. Stable under concurrent writes, no offset drift, sane defaults.
- [SDKs](https://lo.st/api/sdks): Official lo.st SDKs for TypeScript, Python and Go. Generated from OpenAPI, idempotency-aware, retry-safe.
- [Webhooks](https://lo.st/api/webhooks): Subscribe to object.* events with HMAC-signed deliveries, 5-minute replay window, and at-least-once semantics.
- [API quickstart](https://lo.st/api/quickstart): Authenticate, create your first object, and subscribe to a webhook in under five minutes.

## Public

- [Home](https://lo.st/): Report something you lost.
- [Found something](https://lo.st/found): Hand in an item you found.
- [Public feed](https://lo.st/feed): Browse reported lost & found items.
- [Pricing](https://lo.st/pricing): Plans for individuals and venues.
- [About](https://lo.st/about): Operational software, not a consumer toy.

## Public feed — per-item structure

Lost items live at `/lost/{city-slug}/{descriptor-slug}-{short-id}`.
Found items live at `/found/{city-slug}/{descriptor-slug}-{short-id}`.
City hubs: `/feed/c/{city-slug}`. Category hubs: `/feed/cat/{category-slug}`.

Each item page contains: item description, photo (face/plate-blurred), category, general location (city + venue or area), date reported, schema.org Article + Place + BreadcrumbList structured data, and an anonymous bridge-message contact link.

Not on the public feed: owner contact info (replaced by anonymous bridge messages), exact addresses (city-level only), passport / ID / financial documents, active claim verification questions.

## Legal

- [Terms](https://lo.st/legal/terms)
- [Privacy](https://lo.st/legal/privacy)
- [DPA](https://lo.st/legal/dpa)