ashiba.ai
Features ▾
PricingLive demoCase studyAboutSign inStart free
Platform · REST API + MCP

Build on ashiba.

Every operation a builder does in the app is a REST endpoint and an MCP tool. Create a project, price the estimate, record actuals, award bids — from your own code or an AI agent. The same role rules the app enforces, held at the token.
Read the API referenceMCP referenceGet a key
What you can drive

Eleven write operations. The whole read surface.

Projects
create_projectupdate_project
Bootstrap a job and advance its lifecycle. The creator becomes an admin member; a starter checklist is seeded.
Estimate
add_cost_itemupdate_cost_item
Price a line as a band, then record the actual that grades it. The band → actual → verdict math runs identically to the app.
Money loop
add_bidaward_bidadd_paymentadvance_paymentadd_change_orderadvance_change_order
The whole contract loop: award a bid (commits the actual), run the pay-app to paid (settles the line, gated on lien waiver + COI), and sign a change order (lifts the linked band by the added scope so the verdict stays honest).
Field
add_checklist_itemtoggle_checklist_itemadd_schedule_taskadd_log
Populate the checklist, lay out the schedule (self-baselined, so slip starts at zero), and log the day.
Documents
add_document
Push a plan, spec, or contract into a project. HTML is sanitized on write; new docs are private until you publish them.
Read
list_projectslist_cost_itemslist_schedulelist_bids…
The whole read surface too — projects, cost ledger, checklist, schedule, logs, documents, bids, payments, permits.
Close the estimating loop in two calls

Price a line, then record the actual that grades it.

A read+write key carries exactly your access. Recording the actual freezes the original estimate band, so a number entered through the API grades the estimate the same way the app does — no model in the loop, your own numbers.
# Price a labor line as a band curl -X POST https://www.ashiba.ai/api/v1/projects/42/cost-items \ -H "Authorization: Bearer ak_xxxxxxxx_..." \ -H "Content-Type: application/json" \ -d '{ "kind": "labor", "name": "Framing", "est_low": 8000, "est_high": 12000 }' # Later, record the actual off the invoice — the band → actual → verdict math runs curl -X PATCH https://www.ashiba.ai/api/v1/projects/42/cost-items/318 \ -H "Authorization: Bearer ak_xxxxxxxx_..." \ -H "Content-Type: application/json" \ -d '{ "actual": 15000, "status": "paid" }' # → { "data": { "actual": 15000, "verdict": "OVER", ... } }
MCP · for agents

Point Claude — or any MCP client — at your jobs.

The same surface is exposed as Model Context Protocol tools over JSON-RPC at https://www.ashiba.ai/api/mcp. Your key is the bearer token; read tools work with any key, write tools need a read+write key. An agent can set up a job, extract actuals from an invoice, or summarize status — inside the same rules the app holds.
{ "method": "tools/call", "params": { "name": "award_bid", "arguments": { "project_id": 42, "bid_id": 7 } } } // → the winning bid is awarded, its package's other bids declined, // and the amount commits to the linked cost line as the actual.
One rule, held at the token

A sub- or client-scoped key never carries a figure.

A key derives exactly the access its user has in the app. Cost, margin, bids, and payments are manager-only — a sub- or client-scoped key gets a 403 from those endpoints, and cost fields are stripped in the serializer even if a route were ever misgated. The same invariant the app enforces on every screen, enforced identically at the API and MCP boundary. Keys come in two scopes: read, or read+write — a read-only key can never mutate.
Live in v1
The full read surface, plus writes across the object model — projects, cost lines (including recording the actual), bids (add + award), payments, draws, change orders, checklist, schedule, daily logs, documents, permits, inspections, punch, leads, and vendors. Versioned at /api/v1; the shape is stable.
On the roadmap
Team and member management as writes; webhooks. We don't publish endpoints that 404 — if it's in the reference, it works today.
Build the integration your shop actually runs on.
Start freeAPI reference
ashiba.ai
THE BUILDER'S FIELD OFFICE
足場 ashiba — the scaffolding you stand on to build.
PRODUCT
COMPARE
RESOURCES
COMPANY
LEGAL
© 2026 ASHIBA.AI · AUSTIN, TEXAS