Tennis content for publishers
Cover the players your readers care about. We’re building match reports shaped for your publication, delivered straight to your editorial workflow.
In development. Publisher access is not yet open.
Illustrative examples · Fictional match
The match report
General sports desk
Alex Morgan defeated Jamie Lee 6–4, 7–5 in the second round of the Harbour Open, advancing to the quarter-finals.
| Player | S1 | S2 |
|---|---|---|
| A. Morgan | 6 | 7 |
| J. Lee | 4 | 5 |
Morgan won the opening set 6–4 and took the second 7–5 to complete a two-set victory. The result ends Lee’s run at the tournament.
Result first. Concise, neutral language.
The player perspective
Publication following Jamie Lee
Jamie Lee’s Harbour Open campaign ended in round two with a 6–4, 7–5 defeat by Alex Morgan.
| Player | S1 | S2 |
|---|---|---|
| A. Morgan | 6 | 7 |
| J. Lee | 4 | 5 |
The second set went to 12 games, but Lee was unable to take the match to a decider. Morgan moves into the quarter-finals after winning both sets.
Followed player first. Tournament context.
Handcrafted examples of planned editorial profiles, not live generated news.
Build a feed around the players, represented countries and tournaments your audience follows.
Our next step: editorial profiles that shape the angle, length and language of each publisher’s report.
Receive drafts through the API. Review them in your publishing workflow, with corrections and withdrawals tied to the same story.
Your publication has a point of view
A specialist tennis title and a national sports desk need different stories from the same match. That difference should go deeper than the headline.
Planned editorial profiles will guide player emphasis, story structure, terminology and recurring phrases. See the illustrative profiles above.
We’re developing similarity checks across publisher versions and recent stories, so changing a few words won’t count as a different report.
Clear headlines, relevant context and accurate metadata are part of the planned output. Search visibility starts with value for readers; rankings are never guaranteed.
Built around your workflow
Import a story once. Follow its versions. Keep your edits when the source changes. The development API already defines how drafts, corrections and withdrawals reach a publisher.
Explore the API contractFeed API v1 · Development
GET /api/v1/feeds/{feed_id}/items
Authorization: Bearer <server-api-key>
// Resume from your last cursor.
// Apply newer article versions.
// Process removals immediately.Keep credentials on your server. Public access is not enabled.
Focused from the first serve
Our first scope is English reports of completed ATP and WTA singles matches, subject to data coverage and licensing. A separate tennis publication is being built as our first API customer, using the same interface as future publishers.
See how the integration worksProject origins
The original Contentfeed.ai research project received EU support. Read the historical project notice, including its beneficiary, objectives and original funding allocation.
EU funding and project details