Plug our tools straight into yours.

Shared runtime coverage

Tools audited

400

Headless candidates

335

Typed canary tools

21

Executable locally

21

Remote shared capabilities enabled

21

Browser or device dependent

23

Local file and media

30

Network or provider dependent

12

Audit candidates describe extraction potential. Only tested canaries are marked executable. Legacy PHP execution is counted separately.

Application telemetry records metadata only. Submitted text, files, URLs, generated secrets and results are excluded. Remote metrics unavailable from this WordPress page are shown as unavailable, not zero.

Read the machine status · Developer guide · Local SDK · MCP

Local execution

Install the versioned package directly:

npm install https://ursy.io/wp-content/themes/ursy-io/downloads/ursy-runtime-1.0.0.tgz

import { run } from '@ursy/runtime';
const result = await run('percentage-calculator', { value: 200, percentage: 12.5 });
console.log(result);

Download runtime package

Remote execution

Send an explicit HTTPS request to the isolated service. The same typed result is returned with remote execution and retention metadata.

const response = await fetch('https://api.ursy.io/v1/run', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    tool: 'percentage-calculator',
    input: { value: 200, percentage: 12.5 }
  })
});
console.log(await response.json());

Execution OpenAPI · Live service status and limits

One registry, three surfaces

Each tool has one catalogue identity: its method, its interface contract and its limitations. That single record powers the page a person reads, the machine descriptor a client fetches and the configuration a compatible app renders.

Built for Radical

Radical — the URSY desktop — fetches the catalogue, picks a tool by slug, reads its execution contract and mounts the open browser runtime directly. No scraping prose, no guessing which fields a tool expects.

Shared runtime and separate execution

Discovery v1 stays compatible. Discovery v2 exposes audited execution modes and strict schemas for migrated tools. The browser, Node package and new agent service use the same JavaScript functions. Application telemetry excludes request payloads and results.

Heavy services get a different home

Crawling, headless Lighthouse, batch image processing and machine-learning jobs will never be disguised as ordinary WordPress calls. When they arrive, they arrive as a separately approved api.ursy.io worker with authentication, quotas, bounded jobs and SSRF protection.

Open code, honest attribution

The packaged catalogue and browser runtime ship under the MIT licence. If you build on them, say it’s URSY.io and link each descriptor’s canonical tool page, so your users can inspect the method and use the original for free.