Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Racepace icon

Racepace

Required pace, full km/mile splits, negative-split vs even-split strategy, and race-day pacing bands

Unify Dynamics LLC

Documentation
Tools2read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Splits for a sub-4 marathon
Tools called
race_splits
Negative split pace for a 1:45 half, 3% faster second half
Tools called
race_splits
Pacing plan for a 22-minute 5k
Tools called
pacing_bands
What pace do I need for a 50-minute 10k?
Tools called
race_splits

About

Racepace turns a goal finish time and distance into a race-day pacing plan. race_splits returns the required average pace per km and mile, a full even-split table (elapsed and split time at every km and mile), and a negative-split table where the second half runs a chosen percentage faster than the first (2% by default, within the commonly recommended 1-3% range) while still arriving at exactly the goal time — plus the positive-split numbers shown as a cautionary contrast. pacing_bands returns the same idea as a race-day pacing band instead of a single table: a conservative range for the first 20% of the race, a range around goal pace for the middle 60%, and a faster range for the final 20%. Extends the basic pace calculator in Fit with race-day strategy specifically. Keyless; computed locally; nothing stored.

Sources: Computed locally from the goal time and distance given (pacing algebra, standard unit conversions); fully local, zero upstream calls

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

2 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Splits1 tools
  • Race splitsRequired average pace, full km and mile split tables, and negative-split vs even-split pacing tables for a goal finish time and distance.
Strategy1 tools
  • Pacing bandsA race-day pacing-BAND recommendation (not a single number): a conservative range for the first 20% of the race, goal pace for the middle 60%, a…

Information

PublisherUnify Dynamics LLC
CategorySports & fitness
LanguagesEnglish
Built forGlobal (metric and mile splits)
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://racepace.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Bola (Ball)

A fully local Brazilian football history and facts reference — World Cups, Copa América, legends and trivia

Live · MCP + REST9 tools

Gully

A hand-curated Indian cricket reference — IPL, World Cups, rules and trivia

Live · MCP + REST10 tools

Craque

Cartola FC market, players, value picks, fixtures and a budget lineup builder

Live · MCP + REST10 tools

Scoreboard

Scores, schedules, standings and box scores from the leagues' own feeds

Live · MCP + REST8 tools

SoccersAPI (BYOK)

Read football (soccer) leagues, standings, fixtures, live scores, teams, players and top scorers with your own SoccersAPI key

Live · MCP + REST12 tools

APIfootball (BYOK)

Read football (soccer) countries, leagues, teams, players, standings, fixtures, results and top scorers with your own APIfootball key

Live · MCP + REST9 tools

Documentation

Back to top

What Racepace is for

"I want to run a sub-4 marathon — what pace do I need, what should my splits look like, and should I go out even or save something for the end?" Racepace turns a goal time and distance into an actual race-day pacing plan, not just a single average-pace number.

What it does

race_splits takes a goal finish time and a distance (5K, 10K, half, marathon, or any N km/N mi) and returns the required average pace per km and mile, a full even-split table (elapsed and split time at every km and mile), and a negative-split table where the second half runs a chosen percentage faster than the first (2% by default, within the commonly recommended 1-3% range) while still arriving at exactly the same goal time — plus the positive-split numbers shown only as a cautionary contrast, since that's what happens by accident to runners who go out too hard. pacing_bands returns the same idea as a race-day pacing BAND instead of a table: a conservative range for the first 20% of the race, a range around goal pace for the middle 60%, and a faster range for the final 20% — because holding one exact split every single kilometre is unrealistic, and a band still lands the goal time.

What it is not

Not a fitness assessment: it does not know whether the goal time is realistic for this runner — pair it with Fit's pace and race-prediction tools or a recent time trial to sanity-check the goal. General pacing information, not a guarantee of race-day performance, which also depends on conditions, terrain, training and how the day goes.

Privacy policy

Back to top

Racepace — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Racepace is. Racepace is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf to compute race-day pacing plans. You interact with your assistant; the assistant sends us only a distance and a goal time (and, optionally, a split percentage) needed for the calculation.

What we receive. The arguments of each tool call — a distance, a goal finish time, an optional split or band percentage — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is computed on our server and nothing is stored. The pace tables are pure arithmetic on the distance and time you send; nothing is recorded, logged in request bodies, linked to any identity, or used to train anything. No request is forwarded to any third party.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, or any account records. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Racepace — Terms of Service

Effective 28 September 2026. These terms govern use of the Racepace connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Racepace computes race-day pacing plans — required pace, split tables, and negative/even-split pacing strategy — from a goal finish time and distance, using standard pacing arithmetic. It is accessed through an AI assistant or directly over MCP or HTTP.
  2. General information, not a performance guarantee. Pace and split figures are arithmetic outcomes of the goal time and distance you provide; they do not assess whether the goal is realistic and do not account for course terrain, weather, or how race day actually goes.
  3. Acceptable use. Do not use the Service to circumvent rate limits. Automated use within the published limits is welcome.
  4. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  5. Data. Our Privacy Policy describes what we process. In short: your query is answered on our server and nothing is stored.
  6. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  7. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
  8. Governing law. California law; venue in San Mateo County, California.
  9. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/racepace

Support

Back to top

Racepace support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Racepace never asks for them.

Get Racepace

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://racepace.connectorbay.com/mcp
{
  "mcpServers": {
    "racepace": {
      "type": "http",
      "url": "https://racepace.connectorbay.com/mcp"
    }
  }
}