physical-ai-sprint
Registry code: f394b750470f3686
Data for The Physical AI Sprint, a one-day Physical AI hackathon on 2026-08-17 in
San Francisco alongside Actuate SF, hosted by Nebius with NVIDIA, Antioch and Toloka.
- endpoint
- https://www.buildspace.tv/api/mcp
- door code
- 7711cd977b71ccba
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is physical-ai-sprint live?
- Yes — it answered the hub's last check (checked 59m ago). It answered 99% of checks over the last 30 days.
- Is physical-ai-sprint free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does physical-ai-sprint have?
- 5 tools: get_team, search_hackathon, list_projects, get_event_details, list_teams.
- Is physical-ai-sprint safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- get details of a hackathon event
- list hackathon teams with open spots
- list submitted hackathon projects
- search hackathon teams and projects
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_projects reads open 9h ago
List the projects submitted to the showcase, with the track each ran in (simulation only, hardware only, or both), the robots used, demo media, and the team that built it. Optionally filter by track or by robot.
{ "type": "object", "required": [], "properties": { "robot": { "type": "string", "description": "Case-insensitive substring matched against the robots a project used, e.g. \"SO-101\" or \"G1\"." }, "track": { "enum": [ "sim", "hardware", "both" ], "type": "string", "description": "Filter to one track: \"sim\", \"hardware\", or \"both\"." } } }arguments 19 linesget_event_details reads open 9h ago
Get the details of The Physical AI Sprint: the date, start and end times, hosting organizations, the three project tracks, the robot hardware available, the judging criteria, the submission deadline, and how to register.
{ "type": "object", "required": [], "properties": {} }arguments 5 lineslist_teams reads open 9h ago
List the teams taking part in The Physical AI Sprint, with each team's roster, the skills they already have, and the skills they are still looking for. Optionally filter to teams that have room for more members, or to teams seeking a particular skill.
{ "type": "object", "required": [], "properties": { "skill": { "type": "string", "description": "Case-insensitive substring to match against the skills a team is looking for, e.g. \"vision\"." }, "looking_for_members": { "type": "boolean", "description": "When true, return only teams that still have room for new members." } } }arguments 14 linesget_team reads unknown 5h ago
Get a single hackathon team by its slug, including the full roster with GitHub handles, the pitch describing what they want to build, and the URL of the GitHub thread where people ask to join.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The team slug, as returned by list_teams, e.g. \"practice-makes-perfect\"." } } }arguments 12 linessearch_hackathon reads unknown 5h ago
Search across everything at once: team names and pitches, the skills teams are seeking, project titles and descriptions, the robots used, and people by name or GitHub handle. Use this when you do not know whether the answer is a team, a project, or a person.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1, "description": "Maximum number of matches to return. Defaults to 20." }, "query": { "type": "string", "minLength": 1, "description": "Free text to search for, e.g. \"computer vision\", \"SO-101\", or a person's GitHub handle." } } }arguments 20 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf394b750470f3686.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f394b750470f3686/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f394b750470f3686?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.