open-index/open-npm huggingface dataset:
npm package: @relai-fi/plugin-openclaw
Description: OpenClaw plugin for RelAI marketplace — x402 paid API calls
Author: X402RelAI
Latest version: 0.1.2

# @relai-fi/plugin-openclaw

OpenClaw plugin for the [RelAI](https://relai.fi) marketplace. Browse, discover, and call paid APIs with automatic x402 micropayments — supporting both EVM and Solana chains.

## Installation

```bash
openclaw plugins install @relai-fi/plugin-openclaw
```

For local development:

```bash
openclaw plugins install -l ./plugins/openclaw
```

## Configuration

In your OpenClaw gateway config:

```json5
{
  plugins: {
    entries: {
      "plugin-openclaw": {
        enabled: true,
        config: {
          baseUrl: "https://api.relai.fi",   // RelAI platform URL
          requestTimeoutMs: 15000,            // HTTP timeout (default: 15000)
          chainType: "evm"                    // "evm" or "solana" (default: "evm")
        }
      }
    }
  }
}
```

All config fields are optional and have sensible defaults.

## Tools

The plugin registers 4 tools:

### `relai_setup`

Set up an agent key for this agent. Generates a local keypair (EVM or Solana), opens a consent URL in the browser, and polls for approval automatically.

```
> Set up my RelAI agent key
```

Parameters:
- `agentName` — Human-readable name shown in consent UI
- `chainType` — `"evm"` or `"solana"` (defaults to plugin config)
- `contractAddress` — ERC-721 agent NFT contract address (optional)
- `nftTokenId` — Agent NFT token ID (optional)
- `network` — Network name, e.g. `"skale-base"` (optional)

### `relai_discover`

List available paid APIs on the RelAI marketplace.

```
> What APIs are available on RelAI?
```

Parameters:
- `network` — Filter by supported network (optional)

### `relai_api_info`

Get details and endpoint pricing for a specific API.

```
> Show me the endpoints and pricing for the nshield API
```

Parameters:
- `apiId` — API identifier (e.g. `"nshield"`)

### `relai_call`

Call a paid API endpoint. Payment is handled automatically via the service key.

```
> Call the nshield API endpoint /v1/health
```

Parameters:
- `apiId` — API identifier
- `endpointPath` — Endpoint path (e.g. `"/v1/health"`)
- `method` — HTTP method (default: `GET`)
- `body` — JSON request body for POST/PUT requests (optional)

## How it works

1. **Setup** — `relai_setup` generates a local keypair and initiates a consent flow with the RelAI platform. The user approves in their browser, and a service key is issued and stored locally in `~/.openclaw/relai/agent-keys.json`.

2. **Discovery** — `relai_discover` and `relai_api_info` query the RelAI marketplace to find APIs and their pricing.

3. **Calling** — `relai_call` proxies requests through the RelAI relay with automatic x402 payment using the stored service key. The service key works across all chains.

## Data storage

Agent keys are stored in `~/.openclaw/relai/agent-keys.json` with restricted file permissions (`0600`). Override the storage directory with the `RELAI_STORE_DIR` environment variable.

## License

MIT
npm package: @relambda/edge
Description: The builder of AWS Lambda@Edge (Origin Requests) handler for Remix
Latest version: 1.0.2

# Relambda@Edge

The _Relambda@Edge_ is a tiny handler that allows you to run [Remix](https://remix.run/) projects on [AWS Lambda@Edge](https://aws.amazon.com/lambda/edge/).

This package allows you to build infrastructure without forcing you to use a specific IaC library (how it has been done in `@remix-run/architect`).

**NOTE:** the Remix team won't create libraries like this. You can find more info in that [thread](https://github.com/remix-run/remix/pull/3173#issuecomment-1248735404).

## Getting Started

To install the package run the next commands:

```sh
npm i @relambda/edge
```

This package has a peer dependency:

```sh
npm i @remix-run/node # usually it comes with Remix
```

Then you can create handler:

```js
// server/index.js
import * as build from '@remix-run/dev/server-build'
import { createLambdaHandler } from '@relambda/edge'

export const lambdaHandler = createLambdaHandler({
  build,
  mode: process.env.NODE_ENV,
})
```

Don't forget to alter you [Remix Config](https://remix.run/docs/en/v1/api/conventions#server) and add path to the server entry point:

```js
// remix.config.js
module.exports = {
  server: 'server', // path to entry point
}
```

Build and deploy your magic to the AWS Lambda@Edge! 🤠