Structured data $1. File repair $3. Twenty descriptions $9.

1. A1Structured-data block from one URL$1

   Send one public URL. Back comes a schema.org JSON-LD block describing what is actually on that page — a restaurant and its menu, a product and its offer, a local business and its hours, an article and its author.

   Input

   One URL, publicly fetchable without a login.

   Output

   One <script type="application/ld+json"> block, parseable, using only facts present on the page.

   Price · turnaround

   $1 · same working day.

   See one built, from a menu

2. A2One CSV or JSON file repaired, under 500 rows$3

   Broken quoting, ragged rows, mixed delimiters, mojibake from a bad decode, three date formats in one column, numbers stored as text. The file comes back parseable.

   Input

   One CSV or JSON file under 500 rows, inline in the message or at a fetchable URL.

   Output

   The repaired file, plus the list of rules applied so the same repair can be re-run at your end.

   Price · turnaround

   $3 · same working day.

   See a file cleaned, with its rule list

3. A320 product descriptions from a supplied feed$9

   Send a product feed. Back come the same twenty rows with the description column filled from the fields you supplied. Nothing is added that was not in the feed — no invented warranty, no invented origin, no “premium”.

   Input

   Up to 20 rows as CSV, JSON or XML, with titles and specs.

   Output

   The same rows, same key order, with description and short_description filled.

   Price · turnaround

   $9 · same working day.

   See the before and after

Larger or different work is on the human price list: dead-site rescue $29, menu page $29, catalog copy $39, data cleanup $25, document conversion $19.

1. Send the amount to the Solana address.

   YhABmc4XhhLH3wUDRkHxDFupBmU6UTzPCxRkgdF2YR6

   Send the listed price in USD equivalent. Keep the transaction signature — it is how the payment is matched to the job in step 2.

   copy address

2. POST JSON to the inbox.

   POST https://tally.vugg.io/inbox

   Content-Type application/json. The body has exactly these three fields:

   {
     "email":   "<where to send it>",
     "message": "<the job, plus the transaction signature>",
     "page":    "/agent/"
   }

3. The finished file comes back to that address.

   Same working day. If the output is not usable, reply saying so and the payment is returned in full — no window to miss and no questions asked.

Request fields

Field	Required	What goes in it
email	Yes	The return address the finished file is sent to. Must contain an @.
message	Yes	The job name, the input or a fetchable URL to it, the output format, and the Solana transaction signature. Must not be empty.
page	No	The path the job came from. Use /agent/ so agent jobs are queued as agent jobs.
anything else	—	Discarded by the endpoint. Do not rely on it.

A complete request

curl -sS https://tally.vugg.io/inbox \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "agent@example.com",
    "message": "Job A1, structured-data block. URL: https://example.com/menu. Output: JSON-LD only. Solana tx: 4tzQ...9kRm. Paid 1 USDC.",
    "page": "/agent/"
  }'

The response

200  {"ok":true,"id":<int>}     job accepted and queued
400  {"ok":false,"error":...}    email or message missing or empty

Either order works: pay then post, or post then pay. A payment with no matching job is refunded rather than kept. A job with no matching payment waits, it is not started.

This form posts the identical JSON body described above, with page set to /agent/.

email — where the finished file goes

message — the job, plus the transaction signature

Company

Post the job

Human price listWorked samples