# Videographer.org

The second-shooter network. Videographers mark the dates they are free, and other
videographers who are already booked find them for those dates. Nobody here is a
client: every account on this property is a videographer, and the thing being
exchanged is one shift of crew work.

## What an agent can do here
POST https://videographer.org/api/account/second-shooter — Opt yourself in or out of the second-shooter network
POST https://videographer.org/api/account/availability — Mark your own days available or busy
GET https://videographer.org/api/second-shooter — Search the network for an available peer
POST https://videographer.org/api/second-shooter/request — Ask a peer to shoot a date with you
POST https://videographer.org/api/second-shooter/request/{id}/{action} — Accept or decline an inbound request
GET https://videographer.org/api/account/connections — Your crew requests, both directions
GET https://videographer.org/api/read — Read a described gig into the fields a crew search takes
POST https://videographer.org/api/read — Read a described gig, for the shared console script
POST https://videographer.org/api/event — Record a page view

The full contract is https://videographer.org/openapi.json (OpenAPI 3.1). 6 of those
9 operations are videographer.com's crew router, mounted here — the
same code answers them on both properties, so a client written against either
works against both.

## Two things to know before you build against this
1. DELIVERY DEPENDS ON THIS DEPLOYMENT. Asking a peer always writes the
   request and queues a heads-up email with status `queued`; whether that mail leaves
   depends on whether the operator has armed a sender, so do not build on the mail
   arriving. Signing in is the reliable path: the person you asked sees the request in
   their requests list either way. AS DEPLOYED RIGHT NOW: armed — the email is sent, and a failure is recorded on the row rather than swallowed.
2. THE API TAKES A SESSION COOKIE, NOT A TOKEN. The 6 crew operations
   authenticate from a cookie minted at https://videographer.com. That property also serves
   /api/account/agent-credential, which mints scoped tokens. Those tokens DO reach the
   same crew operations on https://videographer.com, whose own allowlist honours them — but NOT here:
   this property mounts the router behind a cookie-only session check, so a bearer
   token gets 401 on videographer.org and works one host over. Measured, not assumed: this
   property resolves the actor from the signed cookie and reads no authorization
   header at all.

## Two paths that are this property's own
GET /api/read reads a described gig — "a 6-hour wedding in Austin, two cameras" —
into the fields a crew search takes, using the same parser videographer.com prices
client work with. It turns words into a search and promises nothing about who is
free.

POST /api/event records a page view and nothing else. It never carries a name, an
id or an email.

## Nothing here is bought, and nothing here is sold
Routing is free in both directions on this property: free to ask, free to accept, no
commission, no cut of a crew booking. Appearing on this network and being found on it
are free and stay free, which is the part that does not change. There is no price, no
checkout and no paid placement here: no position in a search result was paid for, and
this contract exposes no endpoint that charges anybody. What is sold at https://videographer.com is a
page of their own, and it does not affect who a crew search returns today.

## Getting out
Unmarking a day here stops it reaching anybody, immediately, with no request to anyone.
Exporting everything held and closing the listing are the account's own controls and
live at https://videographer.com/account, because that is the property that owns the record. One thing
none of it undoes: accepting a request has already exchanged an email address with that
one videographer, and closing an account does not recall it.

## Being found here is opt-in and off by default
A videographer is discoverable only after switching it on, separately from marking
any date. A search that returns nobody is a real answer about this network, not an
error and not a filter to widen.

## Elsewhere in this network
- https://videographer.com/docs — rendered docs for the crew contract these two properties share
- https://videographer.com/llms.txt — Describe a shoot, get a budget, get matched.
- https://videographer.net/llms.txt — The directory — browse videographers by city and shoot type.