Documentation | Flypost Ground Truth Registry
Flypost Protocol

Documentation

Integrate the system of record for real-world presence. Discovery (Ask), Publishing (Post), and Verification (Presence) are ready for deployment.

01 / Product Surfaces

Flypost Ask

Public, read-only discovery of real estate events via geographic search.

  • Auth: None (Public)
  • Base: ask.goflypost.com
  • OpenAPI: /openapi.json

Flypost Post

Authenticated ingest for publishing structured events via natural language.

  • Auth: Firebase (browser) or x-flypost-write-token (server)
  • Base: api.goflypost.com
  • Rate: 500 req / 15 min

02 / Quickstart

Find Events Near Santa Monica

curl -X GET "https://api.goflypost.com/v1/events/near?lat=34.0195&lng=-118.4912&radius=5"

Publish an Open House

curl -X POST "https://api.goflypost.com/api/parse-and-publish" \ -H "Content-Type: application/json" \ -H "x-flypost-write-token: YOUR_TOKEN" \ -d '{ "naturalLanguageInput": "Open house at 810 Franklin St, Santa Monica, CA on Jan 15 from 1-4pm. https://example.com/listing/810" }'

Tip: Brokerage-scoped write tokens inject x-flypost-brokerage-id automatically. Only include brokerageId manually if your integration uses a multi-tenant/global token.

03 / Authentication

Authenticated operations (Post/Presence) require credentials. For server-to-server publishing, include a static token in the x-flypost-write-token header (or as Authorization: Bearer <token>). For browser publishing on post.goflypost.com, use Authorization: Bearer <firebase_id_token>.

Brokerage Tenancy

Brokerage-scoped tokens inject x-flypost-brokerage-id for data ownership. Discovery requests with a brokerage scope unlock full street-level location precision.

04 / Publishing Best Practices

Recommended Fields

For best results, include: event type (open house), full address, date, start/end time window, and an https:// listing URL when available. List price is optional; never invent prices or details.

Presence Integrity

Each stored event includes a SHA-256 hash (event.hash) for integrity verification. Discovery responses may also expose a hash field (e.g., dataHash) depending on surface/version.