Skip to main content
Status: Planned. Accounts with access can connect when Speedrun Alpha is enabled in ApexGenius. The service needs no API key. Saving this connection does not verify an applicant or submit an application. Explore the Speedrun Alpha connector.

​
Connect and read requirements

Before you start
  • An ApexGenius account with Speedrun Alpha enabled. Public availability is planned.
  • No Speedrun sign-in or API key is needed for public requirements. Applicant email verification is separate.
1

Open Speedrun Alpha in Connections

Sign in to ApexGenius, open Connections, and choose Speedrun Alpha. If it is unavailable, check access with support.
2

Connect the application service

Choose Connect. ApexGenius checks the official service and saves the connection without asking for applicant details.
3

Review tools and your AI access

Keep public requirements and discovery enabled for the first read. Applicant reads and writes start off. Enable them separately only when needed, and give your AI client the corresponding access.
4

Read the current requirements

Open the SpeedrunAlpha skill, ask your AI the question below, and check the result and Tool Activity. Each write needs a separate review.
Try a first question with your AI agent
A successful requirements read confirms public application access. It does not verify an applicant, save a draft, or submit an application.

​
Tools and application skill

Open Skills on the connection to read SpeedrunAlpha, or read that MCP prompt in a compatible AI client. It covers the complete application workflow and does not grant additional tool access. Four ApexGenius tools route nine reviewed native operations: Your AI discovers the enabled tools using apex_search_tools. Read calls use apex_call_read_tool; writes use apex_call_write_tool after approval. Enable applicant tools only when needed and choose the corresponding access for your AI client. An enabled service resource is also required.

​
Applicant access and review

  • Validation: validate_draft sends your answers to Speedrun for checking. It does not save them.
  • Drafts: save_draft replaces the entire draft for the supplied email. Review the complete field set; a partial set is not a patch.
  • Email: Request a code for the applicant’s exact email. The verified applicant receives an intake token for protected application access.
  • Resume: Requesting a signed upload URL does not upload the file. Use your client’s authorized upload capability, or the official application page, then parse and review the extracted facts.
  • Submission: Review the final complete application and current terms. Explicit applicant approval and applicant-entered terms acceptance are required, followed by approval of the exact ApexGenius write.
Keep email codes, intake tokens, parse tokens, and signed upload URLs out of saved skills and application answers. Never infer personal eligibility answers, work authorization, visa needs, cofounder emails, or availability.

​
Check the result

A successful schema read proves access to public requirements. Verified email, a saved draft, uploaded resume, submitted application, and program acceptance are separate results. Report the actual provider response for each step. If a write times out, check its outcome before retrying. If a tool is missing, check provider access, Tools, the enabled service resource, and your AI client’s access. An upstream outage does not require a new provider sign-in. Disconnecting stops future calls and expires outstanding ApexGenius approvals. It does not delete a draft or withdraw a submitted application.

​
Official references

Compatibility does not imply partnership. Speedrun owns its application terms, questions, availability, and selection decisions.
Last modified on September 15, 2026