FREE EXAMPLES · NO SIGN-IN
Explore four sample outcomes for invoices, scans, meetings and document workflows. Download the examples immediately — no password, wallet, credit card or upload required.
Sample 01 · Invoice
See how an invoice could become tabular data. This predefined example is fictional; no real file processing occurs on this page.
EXAMPLE SUPPLIES LLC Invoice: INV-2026-014 Date: 2026-10-12 Paper and office supplies Subtotal: 100.00 USD Tax: 19.00 USD Total: 119.00 USD
| Supplier | Invoice | Date | Subtotal | Total |
|---|---|---|---|---|
| Example Supplies LLC | INV-2026-014 | 2026-10-12 | 100.00 | 119.00 |
Sample 02 · OCR
A prepared illustration of text extraction from a fictional scanned receipt; this page does not run the OCR engine.
SAMPLE OFFICE Receipt: R-0074 Date: 2026-10-16 Paper $12.00 Delivery $3.00 TOTAL $15.00
Supplier: Sample Office Receipt number: R-0074 Date: 2026-10-16 Items: - Paper: 12.00 USD - Delivery: 3.00 USD Total: 15.00 USD Review status: unchecked
Sample 03 · Meeting
A fictional conversation and a prepared, reviewable minutes draft — not an actual recording or live transcription.
00:03 Alex: Please compare the vendor quotes by Friday. 00:09 Taylor: I'll make a summary table. 00:15 Alex: We can choose the supplier on Monday.
Action: Compare vendor quotes Owner: Taylor Due: Friday Decision meeting: Monday Status: Review required Source: fictional dialogue
Sample 04 · Flow
An illustrative workflow for small-business admin. Human review is part of the process; no uploaded files or stored customer data.
30 supplier invoices a week PDF attachments + image scans Manual transcription to a table Follow-up on missing fields Review totals and tax rates
1. Collect allowed documents 2. Extract fields using Flow 3. Review totals / exceptions 4. Export clean CSV/XLSX 5. Human approves final data No automatic bookkeeping or tax advice implied.
These are prepared fictional samples, not live AI output. Actual customer processing is a separate authenticated, credit-metered workflow. Downloading the samples does not spend credits.
Review the pricing and try Skavio's real services when you choose. Developer integration documentation is available publicly.
MORE FREE DEMOS
Four original interactive demos plus 28 additional downloadable before/after examples, grouped by product. Fictional prepared examples, not results from a live processing run.
SUPPLIER NORTH Invoice INV-026 Date 2026-10-05 Net 100.00 USD Tax 19.00 USD Total 119.00 USD
supplier,invoice,date,net,tax,total Supplier North,INV-026,2026-10-05,100.00,19.00,119.00
OFFICE STORE Pencils 4.00 Paper 9.00 Folders 6.00 Staples 2.00 Delivery 4.00 Total 25.00 USD
item,amount Pencils,4.00 Paper,9.00 Folders,6.00 Staples,2.00 Delivery,4.00
PO-2026-011 Buyer: Example Studio Vendor: Paper Warehouse 250 sheets at $0.08 Delivery expected 2026-11-20
po,buyer,vendor,units,unit_price,expected PO-2026-011,Example Studio,Paper Warehouse,250,0.08,2026-11-20
Page 1 Invoice A101 42.00 USD Page 2 Invoice A102 57.00 USD Page 3 Invoice A103 19.00 USD
invoice,total A101,42.00 A102,57.00 A103,19.00
File 1: delivery-confirmation.pdf (one page) File 2: invoice-a101.pdf (one page) Action: pdf-merge
Expected: merged.pdf Pages: 2 Check both originals are present and in order.
Sample pages: introduction, invoice, notes Action: pdf-split Select page 2
Expected: page-2.pdf 1 page extracted Original remains unchanged.
Sample: landscape page Action: rotate Angle: 90 degrees
Expected: rotated.pdf Visual orientation corrected Page content preserved.
Sample: scan containing Item, Date, Amount Action: OCR to searchable PDF
Expected text fields: Item: office supplies Date: 2026-10-16 Amount: 15.00 Review OCR before use.
Spoken example: Send the revised contract on Thursday. Confirm with Alex.
Transcript: Send the revised contract on Thursday. Confirm with Alex.
Caller: Can you send the invoice as a PDF? Agent: I will send it today.
Caller: Can you send the invoice as a PDF? Agent: I will send it today. Speaker verification required.
Q: How do you handle paper invoices? A: We enter them manually into spreadsheets.
00:00 Question: How do you handle paper invoices? 00:04 Answer: We enter them manually into spreadsheets.
Record: Three boxes, twelve units each, total thirty-six units.
Transcript: Three boxes, twelve units each, total thirty-six units. Review numbers against source audio.
Alex: Prototype on Tuesday. Sam: I will review it Wednesday. Lee: Launch decision Friday.
Action: Sam reviews prototype Wednesday. Decision pending: Friday launch. Source: sample conversation.
Buyer: Can delivery be moved to Monday? Supplier: We can confirm by Thursday.
Pending: delivery on Monday. Action: Supplier confirms by Thursday. No final delivery commitment.
PM: Upload test files by Monday. QA: Validate on Tuesday. Team: Review findings Wednesday.
Task 1: Upload files Monday. Task 2: QA Tuesday. Review: Wednesday.
Owner: Account access transferred. Support: Open issue remains on export. Owner: Follow up Friday.
Transferred: access Open issue: export Owner action: Friday follow-up
Instruction: Reply politely, confirm receipt, promise update in 2 days.
Subject: Request received Thank you for your message. We received your request and will update you within two business days.
Completed: 3 invoices, 2 meetings Pending: 1 approval Risk: export delayed
Status: 5 tasks completed. Pending: 1 approval. Risk: export delay. Next step: confirm owner.
supplier;amount A Ltd;12,00 B Ltd;9,50 A Ltd;12,00
supplier,amount A Ltd,12.00 B Ltd,9.50 Duplicate row flagged for review.
Goal: onboard a new supplier. Required: contract, bank data, approval.
[ ] Verify company identity [ ] Review contract [ ] Verify banking details [ ] Get owner approval
Network: Base (8453) Token: USDC Transaction: SAMPLE_NOT_ON_CHAIN Request: evidence check
Status: illustrative only Do not regard this example as an on-chain payment. Production must verify network, token and transaction.
Expected network: Base Received: sample transaction from another network
Expected: reject or unsupported network No payment marked as settled.
Sample: USDC transfer submitted but no confirmed block is available.
Status: pending or unverified Never issue a successful payment receipt before settlement.
Requested: transaction hash, chain, amount, token, timestamp, confirmations.
Validate: tx hash + token contract + receiver + amount + network. Then generate evidence only if confirmed.
GET https://getskavio.com/v1/pricing Accept: application/json
HTTP 200 Content-Type: application/json Review current price catalog and per-operation rates.
Client requests a metered agent tool without a verified payment.
HTTP 402 challenge example Inspect chain, token, recipient, price and expiry. Do not pay without verifying limits.
Request: multiple concurrent uploads Possible response: HTTP 429
Wait for Retry-After when present. Retry idempotently; do not duplicate charges.
Discover available tools and schemas through the published MCP endpoint.
Read tool metadata and required input schema. Authenticate before running tools; enforce credit cap.
These previews are fictional. Upload a real test file in the corresponding app after account verification; the exact credit quote appears before processing.
