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

Frame Time

A hand-curated speedrunning technique & terminology reference — categories, timing, tricks and glossary

Unify Dynamics LLC

Documentation
Tools8read-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.

What's the difference between any% and 100%?
Tools called
category_info
What's RTA vs IGT timing?
Tools called
timing_method
What is sequence breaking in speedrunning?
Tools called
technique_class_info
What does PB mean in a speedrun?
Tools called
term_glossary
How does a speedrun actually get verified?
Tools called
verification_process_overview
What categories and tricks fit a metroidvania?
Tools called
find_category_for_game_type
How did speedrunning start as a hobby?
Tools called
history_note
Give me tips for starting to speedrun
Tools called
beginner_tips

About

Frametime is a fully local, hand-curated speedrunning technique & terminology reference. category_info explains one run category (any%, 100%, glitchless, low%, all bosses, true ending, individual level, co-op, no major skips, category extensions): what counts, common community debates, and related categories. timing_method explains a timing convention (RTA, IGT, loadless/LRT, frame time, start/end trigger convention). technique_class_info explains a generic technique class (sequence breaking, clipping, out-of-bounds, frame-perfect tricks, wrong warp, damage boosting, zipping, arbitrary code execution, RNG manipulation, savestate practice, TAS vs human runs, routing, segmented vs single-segment, movement optimization) conceptually, with a TAS-only flag and legality note. term_glossary defines 25 community terms (PB, WR, splits, autosplitter, verifier, meta, sum of best, and more). verification_process_overview explains generically how a run gets verified and accepted onto a leaderboard. find_category_for_game_type suggests relevant categories and techniques for a genre (platformer, metroidvania, RPG, racing, puzzle, FPS, fighting, rhythm, open world). history_note gives short qualitative notes on the hobby's history. beginner_tips gives an ordered shortlist of practical starting tips. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Hand-curated original description of speedrunning as a hobby and community practice as of build date; 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

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

OpenAPI
Look Up a Concept4 tools
  • Category infoFull detail for one speedrunning category: what counts as meeting it, common community debates about its definition, and related categories.
  • Timing methodExplains one speedrunning timing convention: how it's measured and when it's typically used.
  • Technique class infoExplains one generic speedrunning technique class conceptually — what it is, how it generically works, whether it's TAS-only, and a legality note…
  • Term glossaryDefinitions of common speedrunning community terms — PB, WR, splits, autosplitter, verifier, meta, sum of best, and more.
Guidance & Context4 tools
  • Verification process overviewA generic overview of how a submitted speedrun gets verified and accepted onto a community leaderboard: the typical steps, common rejection…
  • Find category for game typeSuggests which run categories and technique classes are typically relevant for a stated game genre, with a short note on why.
  • History noteShort, qualitative notes on the history of speedrunning as a hobby and community practice — competitive time-trialing's origins, the rise of…
  • Beginner tipsA curated, ordered shortlist of practical tips for someone just starting to speedrun, from picking a game through submitting a first run.

Information

PublisherUnify Dynamics LLC
CategoryEveryday life
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://frametime.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Fiesta (Celebration)

A fully local Mexico + Spain holidays and festivals guide — with a real computed date for Semana Santa

Live · MCP + REST9 tools

Trámite (Procedure)

CURP decoding, RFC basics, and step-by-step guidance for Mexican civic procedures

Live · MCP + REST9 tools

Lotería (Cards)

A hand-curated, original reference for the traditional Mexican game of Lotería

Live · MCP + REST9 tools

Cocina (Cuisine)

A hand-curated Mexican regional cuisine encyclopedia — dishes, chiles, ingredients and food culture by region

Live · MCP + REST9 tools

Jerga (Slang)

A hand-curated Mexican Spanish slang and colloquialism dictionary

Live · MCP + REST9 tools

Cellar

A fully local wine & spirits reference — varietals, regions, pairings, spirits, cocktails, and tasting vocabulary

Live · MCP + REST9 tools

Documentation

Back to top

Frametime — connector documentation

  • MCP endpoint: https://frametime.connectorbay.com/mcp
  • REST API: POST https://frametime.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://frametime.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
  • Health: https://frametime.connectorbay.com/health · Tool schemas: https://frametime.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/frametime · agent@connectorbay.com

What Frametime is for

A hand-curated speedrunning technique & terminology reference — categories, timing, tricks and glossary.

What it does

Frametime is a fully local, hand-curated speedrunning technique & terminology reference. category_info explains one run category (any%, 100%, glitchless, low%, all bosses, true ending, individual level, co-op, no major skips, category extensions): what counts, common community debates, and related categories. timing_method explains a timing convention (RTA, IGT, loadless/LRT, frame time, start/end trigger convention). technique_class_info explains a generic technique class (sequence breaking, clipping, out-of-bounds, frame-perfect tricks, wrong warp, damage boosting, zipping, arbitrary code execution, RNG manipulation, savestate practice, TAS vs human runs, routing, segmented vs single-segment, movement optimization) conceptually, with a TAS-only flag and legality note. term_glossary defines 25 community terms (PB, WR, splits, autosplitter, verifier, meta, sum of best, and more). verification_process_overview explains generically how a run gets verified and accepted onto a leaderboard. find_category_for_game_type suggests relevant categories and techniques for a genre (platformer, metroidvania, RPG, racing, puzzle, FPS, fighting, rhythm, open world). history_note gives short qualitative notes on the hobby's history. beginner_tips gives an ordered shortlist of practical starting tips. Keyless; fully local; zero upstream calls; nothing stored.

What it is not

Not an official product of, or affiliated with, any brand, league, publisher, or organization it may factually mention. Frametime is a hand-curated reference and design tool, not a substitute for an official rulebook, certified instruction, or professional advice. Fully local, zero upstream calls, nothing stored.

Tools

Look Up a Concept

category_info — Full detail for one speedrunning category: what counts as meeting it, common community debates about its definition, and related categories. Use for "what does any% mean", "what's the difference between glitchless and no major skips". Args: name.

timing_method — Explains one speedrunning timing convention: how it's measured and when it's typically used. Use for "what's RTA", "what's the difference between RTA and IGT", "what is loadless timing". Args: name.

technique_class_info — Explains one generic speedrunning technique class conceptually — what it is, how it generically works, whether it's TAS-only, and a legality note — never step-by-step exploit instructions for a specific real game. Use for "what is sequence breaking", "what's a wrong warp", "is arbitrary code execution allowed". Args: name.

term_glossary — Definitions of common speedrunning community terms — PB, WR, splits, autosplitter, verifier, meta, sum of best, and more. Use for "what does PB mean", "what's a ghost in a speedrun", "what's an autosplitter". Args: term.

Guidance & Context

verification_process_overview — A generic overview of how a submitted speedrun gets verified and accepted onto a community leaderboard: the typical steps, common rejection reasons, the roles involved (runner, verifier, moderator), and how appeals usually work. Describes the shared pattern across communities, not any one platform's exact process. Use for "how does speedrun verification work", "why would a run get rejected".

find_category_for_game_type — Suggests which run categories and technique classes are typically relevant for a stated game genre, with a short note on why. Use for "what categories fit a metroidvania", "what techniques matter for racing games". Args: game_type.

history_note — Short, qualitative notes on the history of speedrunning as a hobby and community practice — competitive time-trialing's origins, the rise of tool-assisted runs, charity marathons, and centralized leaderboards. Use for "how did speedrunning start", "when did speedrunning marathons begin".

beginner_tips — A curated, ordered shortlist of practical tips for someone just starting to speedrun, from picking a game through submitting a first run. Use for "tips for a beginner speedrunner", "how do I start speedrunning". Args: count.

Conventions

  • Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
  • Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
  • Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/frametime/support

Privacy policy

Back to top

Frametime — Privacy Policy

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

What Frametime is. Frametime is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated speedrunning technique & terminology reference — categories, timing, tricks and glossary. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, 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 answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. 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 — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. 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.

Children. Frametime is a general-audience service operated by the adult using the assistant.

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

Terms of service

Back to top

Frametime — Terms of Service

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

  1. The Service. Frametime is a fully local, hand-curated speedrunning technique & terminology reference.
  2. A reference, not professional advice. Frametime is an independent reference and hobby/game-design tool, not affiliated with or endorsed by any brand, organization, league, or publisher it may factually mention. It does not provide legal, financial, medical, or safety-certification advice, and is not a substitute for supervised instruction where real physical risk is involved.
  3. Content varies. Rules, terminology and conventions described here reflect commonly-cited general practice; local house rules, regional variants, and official governing-body rulebooks may differ.
  4. Acceptable use. Automated use within the published rate limits is welcome.
  5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
  7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  8. 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.
  9. Governing law. California law; venue in San Mateo County, California.
  10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/frametime

Support

Back to top

Frame Time 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. Frame Time never asks for them.

Get Frame Time

Free · No sign-in · Read-only

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

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