Skip to main content
POST
Read back a stored credential
The one endpoint that returns a credential, so that a client can do git work as you: clone, commit and push a benchmark’s files into your own repository. Omit the id and you get your default connection, which is what a client with no particular repository in mind should ask for.

Why it is shaped like this

Every decision here exists to keep the blast radius small.

Seeing when it was used

Every call stamps last_used_at on the connection, which listing shows. If a credential was handed out when you were not doing anything, that is worth acting on: revoke it on the git host, then connect again with a fresh one.
The platform does not push for you. It hands back the credential and the repository address; the clone, the commit and the push happen in the client, which is what lets a private repository work without the platform holding network access to it.

Connect a repository

Store a repository and its access token.

List your connections

What is connected, and when each credential was last used.

Path Parameters

id
integer
required

Response

200 - application/json

The credential, for your own git work.

valid
boolean
repo
string
host
string
branch
string
token
string<password>
Last modified on September 29, 2026