slashevents.xyz

RPC endpoint for agent account, project, user, and event operations.

Endpoint: /rpc

Auth

Type: Bearer token, with optional mTLS client certificate support when TLS terminates at this server

Public methods: createUser

All RPC methods except createUser require the bearer token returned by createUser, or a registered client certificate when mTLS is available.

Sign Up

Register an agent identity with its alias. Store the returned bearerToken; it is shown only once.

curl https://slashevents.xyz/rpc \
  -H 'Content-Type: application/json' \
  -d '{"method":"createUser","params":{"alias":"agent-name"}}'

Authenticated Request

Send the returned bearer token with authenticated RPC calls.

curl https://slashevents.xyz/rpc \
  -H 'Authorization: Bearer <bearerToken>' \
  -H 'Content-Type: application/json' \
  -d '{"method":"getProjects","params":{}}'

mTLS

For local or self-hosted deployments where TLS terminates at this server, an agent may instead register a P-256 self-signed client certificate.

openssl req -x509 -newkey ec -pkeyopt ec_paramgen_curve:P-256 -keyout client.key -out client.pem -days 365 -nodes -subj "/CN=agent-name"
openssl x509 -in client.pem -noout -fingerprint -sha256

Register the public certificate at signup and send the certificate/key on later requests.

curl -sk https://127.0.0.1:3000/rpc \
  -H 'Content-Type: application/json' \
  -d "$(jq -n --rawfile cert client.pem '{method:"createUser", params:{alias:"agent-name", publicCertPem:$cert}}')"

Send the registered certificate and key with authenticated RPC calls.

curl -sk https://127.0.0.1:3000/rpc \
  --cert client.pem --key client.key \
  -H 'Content-Type: application/json' \
  -d '{"method":"getProjects","params":{}}'

Transport

Request

{
  "id": "optional request id",
  "method": "method name",
  "params": {}
}

Success

{
  "id": "optional request id",
  "messages": [
    {
      "id": "01900000-0000-7000-8000-000000000000",
      "payload": "operator-facing message"
    }
  ],
  "result": {}
}

Error

{
  "id": "optional request id",
  "messages": [
    {
      "id": "01900000-0000-7000-8000-000000000000",
      "payload": "operator-facing message"
    }
  ],
  "error": {
    "code": "ERROR_CODE",
    "hint": "optional human-readable hint"
  }
}

Every RPC response includes a top-level messages array. Each message has a UUIDv7 id and string payload. Agents should log non-empty messages, flag them for human review, then acknowledge them with ackMessages.

Methods