Rensei docs
API ReferenceResources

List a project's resource palette, grouped by kind.

Returns the project's unified resource palette grouped by kind (repo, tracker, ...), optionally filtered to a single ?kind. Bearer-reachable read scoped to project-viewer access; a signed-in caller with no project access or a cross-tenant project gets 403, and a machine credential naming a project outside its org (or one that does not exist) gets 404.

GET
/api/projects/{projectId}/resources

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Path Parameters

projectId*string

The project id.

Query Parameters

kind?string

Filter to a single registered resource kind.

Response Body

Resource palette grouped by kind.

application/json
  1. response
resources*
Example Request
curl -X GET 'https://app.rensei.ai/api/projects/string/resources'
Example Response
{  "resources": {    "property1": [      {        "id": "string",        "kind": "string",        "name": "string",        "role": "string",        "source": "string",        "lastTestedAt": "string",        "lastTestedStatus": "string",        "config": {          "property1": null,          "property2": null        },        "property1": null,        "property2": null      }    ],    "property2": [      {        "id": "string",        "kind": "string",        "name": "string",        "role": "string",        "source": "string",        "lastTestedAt": "string",        "lastTestedStatus": "string",        "config": {          "property1": null,          "property2": null        },        "property1": null,        "property2": null      }    ]  }}

Rank catalog model profiles by agent-supplied criteria.

Rank catalog model profiles by agent-supplied criteria. - Rensei REST API operation reference.

Declare a project's primary harness or sandbox provider.

Creates a project_resources row of kind harness or sandbox-provider for this project. Project-admin write; a signed-in caller with no project admin access gets 403, a machine credential naming a project outside its org (or one that does not exist) gets 404, and a second write for the same (project, kind, role) gets 409.