Endpoints
Endpoints represent AI services or APIs that tests execute against. They define how Rhesis connects to your application, sends test inputs, and receives responses for evaluation.
For code-first endpoint registration using decorators, see the Connector documentation.
Properties
| Property | Type | Description |
|---|---|---|
id | str | Unique identifier |
name | str | Display name |
description | str | Endpoint description |
connection_type | ConnectionType | How Rhesis connects: REST, WebSocket, GRPC, or SDK |
url | str | Endpoint URL (for REST/WebSocket/GRPC) |
project_id | str | Associated project ID |
Connection Types
| Type | Description |
|---|---|
REST | HTTP API endpoints |
WebSocket | Real-time WebSocket connections |
GRPC | gRPC service endpoints |
SDK | Functions registered via the Connector decorator |
Fetching Endpoints
Invoking Endpoints
Send test inputs to an endpoint and receive responses:
Response Structure
The invoke() method returns a standardized response:
Testing Endpoint Connectivity
Verify an endpoint is responding correctly:
Creating Endpoints
Create endpoints programmatically:
Running Tests Against Endpoints
Execute test sets or individual tests:
SDK-Registered Endpoints
When using the Connector, functions decorated with @endpoint appear as SDK connection type endpoints:
These endpoints can be fetched and used like any other: