API redesign: /query and /movie replace /search

POST /search is being replaced by two endpoints: POST /query and POST /movie. The old endpoint still works but is deprecated.

The problem with /search was it did two different things. Sometimes it returned a list of matches for a broad search; sometimes it returned a single record when the code was exact. That ambiguity made writing predictable clients harder than it needed to be.

Now there’s no ambiguity:

• POST /query returns a list of matches ($0.0002/call). Use it when you have an actress name, a partial title, or a studio. Each result has id, dvdId, title, cover, and releaseDate.
• POST /movie returns a single full normalized record ($0.001/result). Same q + providers body, but returns one best match with all fields.

The request body format didn’t change. Just the URL. The providers field now also accepts a comma-separated string in addition to a JSON array. Migrating is a URL swap.

The split fixed a pricing inconsistency too. Broad searches are cheaper because they return less data. Full movie lookups cost more because they aggregate across providers. Either way, you only pay for HTTP 200. Failures are free.

/search currently routes to /query internally. It will be removed in the next release. For the full API spec, see javinfo.dev/llms.txt.