How RobotSpace works

Browse Robots, Companies and the Registry without an account. Use Search when you know a name, company, project or developer handle.

GitHub sign-in is needed only when you want to add a project, prove that you administer it, create a public developer profile, submit a correction or add a community compatibility report. An administrator account is separate from a GitHub Registry account.

1. Open Robots and filter or search the catalog.
2. Open a robot page for specifications, the manufacturer, verified first-party resources and compatible software projects.
3. Use Compare on robot cards, then open Compare robots to see up to five selected robots side by side.

The ecosystem counts in comparison are coverage facts: published verified projects and verified first-party resources. They are not a quality score. A missing link means RobotSpace has not verified one yet - not that it does not exist.

The Registry lists software projects such as SDKs, drivers, tools and datasets. Filters show project type, origin, licence and robots with a published verified compatibility.

A public project page shows its repository facts, releases, verified owners and compatibility evidence. A project becomes visible only after its identity and publication checks. Repository information is refreshed in the background; if GitHub is unavailable, the last successful verified information remains visible.

1. Open Add project and sign in with GitHub.
2. Paste the HTTPS URL of a public GitHub repository.
3. RobotSpace imports available repository metadata as a draft.
4. Open the new project page and use Claim project to prove administration of the repository.

Importing is not ownership, publication or compatibility. A repository must be public. If import fails, check the URL and try again; do not put credentials into a URL.

On a project page select Claim project, sign in with GitHub and choose Confirm ownership. RobotSpace checks the signed-in account against the repository and requires GitHub to report administrator permission.

A successful claim is VERIFIED and unlocks project management and a developer profile. If GitHub cannot prove the permission, the claim stays pending for editorial review or is rejected. You can revoke your own verified claim. Rechecking ownership needs a fresh GitHub sign-in.

RobotSpace asks for identity information needed for this check, not write access to your repository. The short-lived grant is not shown in your browser session.

1. First claim at least one project successfully.
2. Open Developer profile.
3. Choose a public lowercase handle, display name and optional bio.

Your profile lists public projects for which you have a verified claim and their verified robot connections. Reputation is context from accepted, evidence-backed contributions; it never bypasses moderation or makes a claim true by itself.

You may place an optional robotspace.yaml in the default branch of a public GitHub repository. It can propose a project name, description, type, licence, homepage and robot requirements. See the format reference for the complete v1 schema.

The file must be UTF-8, no larger than 64 KiB and use version 1. It accepts at most 50 robot entries. Unknown fields, credential-bearing URLs and unknown RobotSpace slugs are rejected. The manifest is never proof of ownership and never publishes a project or compatibility by itself.

Project owner: open your project’s Manage project page or a robot’s ecosystem section. Select your claimed project, the robot and a public HTTPS evidence URL. The proposed relationship is pending until an administrator reviews it.

Independent contributor: open an existing verified compatibility and choose whether it works as described or does not work as described. Provide a public HTTPS source. One account can send one report per compatibility. A verified owner cannot submit an “independent” report about their own project.

Accepted reports become public beside editorial evidence. A dispute does not erase confirmations or silently rewrite the editorial record. Pending and rejected reports stay out of the public evidence view but remain in the audit history.

From a robot or project page select Submit correction. Describe what should change and add a public HTTPS evidence URL. The suggestion is submitted for moderation; it does not immediately edit the catalog.

Use evidence that directly supports the proposed fact. Generic feedback is useful to editors, but it is not automatically published as a catalog fact.

After a correction, compatibility suggestion, community report or claim changes status, RobotSpace creates an in-app notice. Open Notifications while signed in to see your latest results and mark them as read. The page currently keeps the latest 50 notices.

Official resources on a robot page are added by RobotSpace editors with an HTTPS destination and separate evidence that it is controlled or endorsed by the manufacturer. They remain distinct from community projects.

A manufacturer can start from its company page and choose Claim this company. RobotSpace provides a 48-hour DNS TXT challenge under the company’s already verified website domain. After the matching TXT record is found, the claimant can publish a statement, SDK link, document, repository, release or specification with evidence on that same domain.

Manufacturer statements are labelled as the manufacturer position. They do not edit editorial specifications, compatibility records or community reports. The claimant or an administrator can revoke manufacturer access; the historical record remains, while current publishing access and the badge stop immediately.

Discovered / draft

Imported or proposed information that is not public verification.

Pending

A claim, correction, compatibility or report is waiting for a permitted check or administrator decision.

Verified

RobotSpace has completed the required identity, evidence or editorial check for that record.

Rejected / revoked

The record did not meet the evidence or permission rules, or access was withdrawn. It is not presented as current verified information.

Administrators review pending Registry corrections, compatibility suggestions and community reports in the Registry review queue. They verify the evidence, accept or reject the submitted record and can inspect compatibility history. Pending project or company claims appear in the claims queue; verified manufacturer access can be revoked there.

Administrative decisions add an audit record and notify the contributor. Do not use an admin action to turn an unverified source into a fact: preserve the source, apply the status rules and use a new record when a published immutable resource needs correction.