Pass and move
Scan before receiving, then move into a new passing lane.
PlayPath indexes your existing video, drills and articles — rugby, football, netball, swimming, whatever your catalogue covers — then answers your members' questions and builds practical session plans inside your own product, with citations that point back to your content, on your domain.
No migration. Your catalogue stays where it is.
“Build a 60-minute U16 skills session for 20 players. Focus on passing under pressure, with cones and balls only.”
Click a chip — or hit ↑ — to see PlayPath answer in real time.
Live answers use our rugby demo catalogue and the same retrieval engine as your integration. Requests are rate-limited; this question box makes a live AI request.
The same retrieval that answers questions also builds sessions — on a canvas the coach can talk to, nudge section by section, or simply overrule. Below is a recording of the real builder, running the four things coaches actually do to a plan.
60-minute U16 skills session, 20 players. Passing under pressure. Cones and balls only.
Searching your library for passing-under-pressure work at U16.
retrieve_content · 14 matchesBuilt a five-section session. Every drill below is one of yours — open a chip to check it before Saturday.
Section 02 needs more pressure — they're too comfortable in a 3 v 1.
Tightened 02 to a 3 v 2 and cut the channel. Sections 01 and 03-05 are untouched.
You rewrote the cue on 04. I've left it alone and put my version up as a suggestion instead.
Waiting on the first section
Scan before receiving, then move into a new passing lane.
Draw a defender before releasing to the free player.
Hold two defenders, then release into the overload before it closes.
Keep a second passing option alive after the first release.
Recognise and use space before the defence recovers.
Call it early — don't wait for the gap to be obvious.
Eyes up at the restart. Where is the extra attacker?
Transfer the scanning and support into a less constrained game.
The coach edited the cue on 04 by hand. That stamps coach authorship, so the assistant's next write to that section arrives as a suggestion to accept or dismiss — never as a silent overwrite.
A recording of the builder with a rugby example, replayed in the browser — no model call is made on this page. In the product the canvas is driven by your own catalogue, and every citation opens the real item. Coaches review suitability before any session is run.
You keep your CMS, your player, and your paywall. PlayPath sits alongside them and does the retrieval.
Send bounded public metadata — id, title, topics, coach, availability — to
/api/v1/content-parents/batch. Write-only credential. No member
data leaves your side.
Embeddings plus an entity graph connect drills to concepts to coaches — so a question about the breakdown, the high press, or the pick-and-roll finds the clip that never used those words. The vocabulary is learned from your catalogue, not hard-coded per sport.
One GET for a streaming answer, or the WordPress plugin if you'd
rather not write any client code at all.
Every one of these runs against your catalogue, in your sport, scoped to your organisation. Turn on what you want; the rest stays dark.
Members ask in plain language and get a written answer with the exact clips and passages it drew from. Every citation resolves to a URL on your domain — the answer sends traffic into your library, not away from it.
Ranks your catalogue per member from what they've actually assigned, watched and finished — then rotates, so a returning coach never gets the same three cards twice. Retired content is filtered out before it can be offered.
Members assemble a session on a canvas of phase-coloured blocks — warm-up through cool-down — pulling drills straight out of your library as references. Every change snapshots a revision, so a plan can be walked back, and plans carry their squad with them across a coaching staff.
A coach uploads whatever match file their analyst produced — no fixed template — and gets structured stats plus a written narrative that points at the drills in your library which address what went wrong.
A tool-calling assistant that holds context across sessions — the age grade being coached, what was worked on last week, which drills already landed — so members stop re-explaining themselves every time.
Members organise players into squads and groups, share plans across a coaching staff, and carry age-grade and level context into every answer the assistant gives them.
Every endpoint is scoped. Your ingestion credential can write catalogue and never read an answer; your read credential can never write. Turn on only the groups you use.
telemetry:ingest
Write-only. Public metadata and activity signals — never member records.
/api/v1/content-parents/batch
Catalogue hierarchy — which chapters belong to which course.
/api/v1/recommendation-contents/batch
Rankable content: title, topics, coach, availability, published date.
/api/v1/source-activity-events/batch
What members assigned, opened, played or finished. Drives ranking.
chat
Retrieval-grounded answers with sources.
/api/rag/stream
Server-sent events. Sources arrive before the prose.
/api/rag/chat
The same answer as one JSON response, when you cannot stream.
recommendations:read
Personalised, rotating slates per member and surface.
/api/v1/recommendations
A ranked slate for one member on one surface, with a reason per item.
chat
Multi-turn coach sessions that keep context between visits.
/api/conversations
Open a session for a member.
/api/conversations/:id/messages/stream
Add a turn and stream the reply, tool calls included.
/api/conversations/:id/blocks
Write session-plan blocks directly, stamped with coach authorship.
/api/end_user_profiles
Upsert a member profile so answers land at the right age grade and level.
content:read content:write
Read or manage the indexed items themselves. Separate scopes, so read access never implies write.
/api/items
List and inspect what PlayPath has indexed for you.
/api/items
Create, update or remove an item. Content changes trigger re-embedding.
$ curl -N "https://playpath.io/api/rag/stream" \ --get \ --data-urlencode "message=Why is our scrum collapsing?" \ --data-urlencode "api_key=$PLAYPATH_KEY" event: content_source data: {"type": "shared_sample", "organization_name": "The Rugby Site", "organization_slug": "the-rugby-site", "read_only": true} data: The most common cause is the tighthead data: binding late. Three drills in your data: library address exactly this… # The content_source event lands first, so you can paint # citations before the prose arrives. 4,000 char cap on message.
Every query, embedding and recommendation is scoped to your organisation. One tenant's content is never reachable from another's credential.
Keys carry explicit scopes — chat, ingestion, recommendations — and default to deny. An ingestion key cannot read answers.
Ingestion takes id, title, topics, coach and availability. No member records, no recipient data, no paywalled body text.
Sign up for immediate access. Explore the sample library, then add your own content and try it before writing any integration code.
Coaching on your own? Sign up as a coach →