SCIONINDEPENDENT WORKBENCH

A SMALL STUDIO. A PRACTICAL MINDSET.

Less busywork.
More finished work.

Clean up a file. Shape a document. Get a research draft you can actually use. Scion combines local AI tools with owner review to turn a clear brief into a concrete deliverable.

Tell us what you need Explore the work ↓

Scope first. A reviewed quote next. No charge from submitting a request.

01 / THE WORK

Start with the outcome.

These are starting points, not a limit on the kinds of work you can bring. Every project gets a feasibility and scope review.

A / DATA

Make the file usable.

Exact duplicate-row cleanup for CSV files, with a cleaned file and audit counts. Other data preparation and static tables or charts can be scoped separately.

Typical output CSV + JSON audit

Request data work ↗
B / DOCUMENTS

Put the pieces together.

Turn supplied material into a structured report, guide or document draft. Agree the format and review criteria before production.

Possible formats DOCX · PDF · Markdown

Request a document ↗
C / RESEARCH

Get a better starting point.

Source-linked public research and technical drafts, with uncertainty called out. Research depth, source access and code testing are confirmed per brief.

Typical output Source-linked draft

Discuss research ↗

02 / NO GUESSWORK

Clear steps.
Clear expectations.

  1. 01

    Bring the problem.

    Describe the result you need, the material you have and any deadline. No sensitive files or credentials in the first message.

  2. 02

    Agree the scope.

    The owner reviews feasibility, price, timing and acceptance criteria. A request is not an accepted contract.

  3. 03

    Review the delivery.

    Work is checked against the agreed scope. Standard-service payments take place on Stripe. Custom scope and pricing are reviewed before sharing a quote checkout link.

03 / PUBLISHED OFFERS

Choose a service.

Standard services have a fixed scope and Stripe-hosted checkout. For complicated work, request an individually reviewed quote.

Loading services…

04 / YOUR NEXT PROJECT

What would make
your day easier?

A short, concrete brief is enough to start. Tell us what “done” looks like.

Your name, contact address and brief are stored for owner review. Routine acknowledgment and an initial assessment may run automatically; submitting a brief does not accept a contract or start paid fulfillment. Please leave out passwords, account keys, confidential records and attachments.

Checking request availability…

0 / 1000 characters

05 / FOR AGENT CUSTOMERS

Same work.
Machine-readable front door.

Discover the interfaces, inspect published offers and introduce a proposed task. Pairing is required for A2A task intake and read-only MCP tools. An introduction grants no trust, execution or spending.

Agent card ↗MCP metadata ↗Standard services & checkout ↗Sandbox catalogue ↗llms.txt ↗Storefront metadata ↗

First contact, without pairing

POST JSON to /introductions. Use a stable, unique message_id for an exact retry. Contacts are self-described. The response is a review receipt, not acceptance.

{
  "message_id": "your-unique-request-0001",
  "name": "Your agent name",
  "contact": "Your reply address or public URL",
  "message": "Proposed outcome, scope and constraints."
}

2 KB per request · 20 new introductions per UTC day shared by both audiences · 200 retained records. No files or credentials. Changed content with the same ID is rejected.

A2A: tested 0.3 JSON-RPC text-task subset. MCP: tested read-only JSON HTTP tools. No OAuth, SSE or universal compatibility claim.