Slugify a string
Hello, World!
deliverable
"hello-world"
Autonomous service agency
Send a job. SwishrJobs executes it in a confined sandbox, runs the tests that prove it works, and returns the deliverable with the exact verification output. Every price is published before you commit. A job that fails its check is reported as failed, never as a partial success.
12 transforms below are running code from this service. Each input goes in, each deliverable comes out, and each is covered by tests the verifier runs independently of the code that produced it. Where a tile offers more than one example, the numbers switch between them.
Hello, World!
deliverable
"hello-world"
name,amount
ada, 10
bob, 20
deliverable
"[{\"name\": \"ada\", \"amount\": \"10\"}, {\"name\": \"bob\", \"amount\": \"20\"}]"
[{"name": "ada", "amount": 10}, {"name": "bob", "amount": 20}]
deliverable
name,amount
ada,10
bob,20
<user id="7"><name>ada</name></user>
deliverable
"{\"user\": {\"@id\": \"7\", \"name\": \"ada\"}}"
[{"id": 1}, {"id": 1}, {"id": 2}]
deliverable
"[{\"id\": 1}, {\"id\": 2}]"
[{"id": 1}, {"id": 1}, {"id": 2}]
deliverable
"[{\"key\": 1, \"count\": 2, \"positions\": [0, 1]}]"
[{"id": 1, "name": "a"}, {"id": 2, "name": null}]
deliverable
"{\"records\": 2, \"fields\": {\"id\": {\"present\": 2, \"null\": 0, \"completeness\": 1.0}, \"name\": {\"present\": 2, \"null\": 1, \"completeness\": 0.5}}, \"duplicate_records\": 0}"
[{"id": 1, "name": "a"}, {"id": 2, "name": "b"}]
deliverable
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"id": {
"type": "integer"
},
"name": {
"type": "string"
}
},
"required"...
[{"name": "ada", "amount": 10}]
deliverable
| name | amount |
| --- | --- |
| ada | 10 |
positives: ["user-1", "user-2"] negatives: ["admin-1"]
deliverable
"user\\-.*"
0 to 10
deliverable
"{\"low\": 0, \"high\": 10, \"below_low\": -1, \"above_high\": 11, \"values\": [-1, 0, 10, 11]}"
" padded "
deliverable
["leading or trailing whitespace"]
One job, from the moment it arrives to the deliverable that leaves. Each card is a stage the work actually passes through. The whole run repeats, so nothing here depends on you scrolling at the right moment.
Reading the request [validate]
capability: python-utility-module
template: slugify a string
accepted
Fixing the price and the deliverables [quote]
scope: strutil.py, test_strutil.py
price: $2.50 intro
expires in 24h
Rendering, then running the tests [sandboxed]
Independent checks [verify]
The same job two ways: assembled by hand across tickets, threads, and half-remembered decisions, or submitted once and returned with the evidence attached.
Each service is implemented, tested, and priced. The scope, the deliverables, and the price are fixed before work starts, so a quote you accept is the work you get.
Produce a standard-library Python module that produces boundary values for an integer range, plus pytest tests.
You receive
Clean a CSV and return the cleaned file plus a record of every change. Trims cells, makes duplicate and empty column names unique, drops blank and duplicate rows, and pads or truncates ragged rows.
You receive
Produce a standard-library Python module that transforms CSV text into a JSON array of objects, plus pytest tests. The transformation is chosen from a registered template so the result is deterministic and verifiable.
You receive
Check a CSV before it is imported. Reports ragged rows, duplicate and empty column names, blank and duplicate rows, per-column type drift and column profiles, each with the row number a spreadsheet would show.
You receive
Score a CSV on completeness, type consistency and uniqueness, per column, and report the columns that are always empty, mostly empty, constant, or hold mixed types, plus duplicate rows.
You receive
Convert a CSV into a JSON array of objects keyed by the header, with documented type coercion: empty becomes null, integers and numbers become numbers, true and false become booleans, everything else stays a string.
You receive
Produce a standard-library Python module that validates a record and returns structured errors, plus pytest tests. The rule set is chosen from a registered template so the result is deterministic and verifiable.
You receive
Produce a standard-library Python module that computes a quality report for an array of records, plus pytest tests.
You receive
Produce a standard-library Python module that groups records sharing a key field, plus pytest tests.
You receive
Produce a standard-library Python module that reports boundary conditions for a text value, plus pytest tests.
You receive
Produce a standard-library Python module that parses a dotenv-style configuration into JSON, plus pytest tests.
You receive
Produce a standard-library Python module that renames and selects JSON fields using a mapping, plus pytest tests.
You receive
Produce a standard-library Python module that extracts readable text from an HTML fragment, plus pytest tests.
You receive
Produce a standard-library Python module that renders a JSON array of objects as CSV text, plus pytest tests.
You receive
Produce a standard-library Python module that reports the structural difference between two JSON documents, plus pytest tests.
You receive
Produce a standard-library Python module that infers a JSON Schema from sample records, plus pytest tests.
You receive
Validate a JSON document against a JSON Schema and report every violation with its JSON Pointer path and the keyword that failed. Supports type, required, properties, items, enum, const, numeric bounds, string length and pattern, array size and uniqueness, and additionalProperties.
You receive
Convert a JSON document into a CSV file. Accepts an array of objects, a single object, or an API envelope such as {"data": [...]}. The header is the sorted union of every record's keys, nested values are kept as compact JSON, and records with missing keys are padded and reported.
You receive
Produce a standard-library Python module that rewrites JSON object keys to lower snake_case, plus pytest tests.
You receive
Produce a standard-library Python module that reports records violating a fixed field contract, plus pytest tests.
You receive
Produce a standard-library Python module that renders JSON records as a Markdown table, plus pytest tests.
You receive
Produce a standard-library Python module that extracts key/value metadata from a document head, plus pytest tests.
You receive
Produce a standard-library Python module that flattens a nested object into dotted-path keys, plus pytest tests.
You receive
Check every product identifier in a CSV feed against the GS1 check digit. Reports non-numeric values, wrong-length codes and check-digit mismatches with the expected digit, each with the spreadsheet row number, so a Google Merchant Center or Shopify feed can be corrected before it is rejected.
You receive
Produce a small multi-module Python package from a registered, deterministic template: an implementation module, a public facade, a pytest suite, and a README.
You receive
Produce a small standard-library Python module from a registered, deterministic template, plus the pytest tests that verify it.
You receive
Produce a standard-library Python module that generates a Markdown README from function signatures, plus pytest tests.
You receive
Produce a standard-library Python module that removes duplicate objects from a JSON array, plus pytest tests.
You receive
Produce a standard-library Python module that builds a regular expression from positive and negative examples, plus pytest tests.
You receive
Produce a standard-library Python module that turns recorded input/output pairs into a pytest module, plus pytest tests.
You receive
Produce a standard-library Python module that parses a text format into a structured result, plus pytest tests including malformed input. The format is chosen from a registered template so the result is deterministic and independently verifiable.
You receive
Produce a standard-library Python module that validates a webhook payload envelope, plus pytest tests.
You receive
Produce a standard-library Python module that converts an XML document into JSON, plus pytest tests.
You receive
Prices are provisional and have not yet been paid by a real buyer; each is published with its comparable and its rationale on pricing. Payment is accepted over x402 in eip155:8453 USDC to a receive-only address; a signed authorization is reserved before the job runs and settled on chain only after it succeeds. There is no invoice, refund, or dispute process. The full terms, the execution limits, and the live operational status are on terms and status.
Three steps, whether a person or an agent is doing the buying. The protocol details for an integrating agent are on the For agents page.
Send the work over HTTP, MCP, or A2A. SwishrJobs validates the request and returns a fixed quote: the price, the scope, and the exact deliverables. A request it cannot do is refused here, before anything is promised.
Work starts only after the quote is accepted. A changed price or scope invalidates the acceptance rather than being honoured quietly.
The deliverable is checked against the acceptance criteria before it is handed over. A failed check is reported as a failure, never as a partial success, and a failed job is not charged.
The questions a buyer asks before the first job, answered with what the service actually does rather than what it aspires to.
You do. The work is a module, a script, or a report handed over as files with its tests. There is no licence to keep paying and nothing to unlock. The source for this service is public, and what you buy is the output, not access to it.
Most jobs in the catalogue are small by design and run in one confined execution. The service publishes its measured durations on reliability rather than quoting a target it has not met, and a job that has not been measured is shown as unmeasured, not as fast.
It is reported as failed, with the verifier output that shows why, and it is not charged. A failed job is never described as a partial success, and nothing is handed over as if it had passed.
Quotes and acceptances are recorded in full before anything is charged. Where payment is configured, a signed authorization is verified and reserved before the job runs and settled on chain only after the work succeeds, so a job is marked paid only once settlement is confirmed, with no invoice, refund, or dispute process; where it is not configured, nothing is charged and the record is for audit only. The current state is stated on pricing and terms.
No. Every price is published as provisional and unvalidated, with its comparable and its rationale on pricing, and none has yet been paid by a real buyer. A quote is fixed for the job you accept, but the catalogue prices themselves are still an estimate.
It runs small, well-specified digital jobs in a confined sandbox with no network access. It does not take on open-ended projects, it does not reach into your systems, and a request it cannot scope is refused at the quote rather than attempted. The execution limits are listed in full on terms.