meta-council.com

Submit a question or decision to Meta Council.

List all available expert panels with their descriptions and agent counts.

List all available expert agents with their roles, domains, and specialties.

Get the full results of a previous Meta Council session, including all agent opinions and the synthesis.

Fetch a chart artifact generated by a council session or LOCUS determination.

List available multi-step workflow pipelines (composable bundles that chain several steps, each able to run on its own model/provider).

Preview what a workflow WOULD do, without running it.

Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it.

Start a multi-step workflow pipeline and return its session id immediately by default.

Poll a previously started workflow run for its current step-by-step status and output (useful when run_workflow timed out or is awaiting a checkpoint).

Recommend the best expert panel for a query (semantic match with keyword fallback).

Estimate what a panel or saved workflow would cost before running it: returns a per-agent/per-step price breakdown, the total for the requested number of runs, your remaining quota and platform credit, an honest list of any models the platform could not price, and a go/no-go decision.

Full detail on one expert agent by slug (from list_agents): role, description, default model, domain, tags, and tools.

Advance a workflow past a human checkpoint — approve or reject the paused step so the pipeline continues.

Continue a stalled or finished workflow run from a chosen step.

Get the authenticated user's Meta Council settings — preferred model, plan tier, which credentials are saved (not live-verified), and the registry-backed tools that require, optionally use, or do not use account credentials.

List which outside services the authenticated user has connected — ticket boards, stored connector credentials (name, kind, whether configured, and when last verified) and the connectors available to call them.

Report the scopes, plan tier, expiry and remaining quota of the API key making this call, so an agent can check what it is allowed to do before attempting it rather than by being refused.

Replace the API key making this call with a fresh one carrying the same scopes.

Mint a short-lived child API key for a delegated subtask.

List the authenticated user's outreach campaigns with live lead / sent / reply counts.

Search the user's outreach leads — filter by a text query (company / contact / email), pipeline status, and/or campaign.

Outreach summary for the user — total leads, sent, replied, and reply rate.

Score an anonymized adult mental-health / addiction case against LOCUS.

Compute a LOCUS Level of Care from dimension ratings you already have.

Request fixed legacy Themis source/citation records and attach a proposed Laws & Regulations agent/source/synthesis plan whose routes are planned_not_run.

Pipeline-stage breakdown for one outreach campaign — total / sent / active / won / lost, reply rate, and per-stage lead counts.

List automation triggers (auto-reply rules, status updates, notifications) configured for an outreach campaign.

List sent / received emails for an outreach campaign, newest first — subject, body preview, and reply classification.

Create a new outreach campaign owned by the authenticated user.

Add a single lead to the authenticated user's outreach book.

Assign one or more of the user's existing leads to one of the user's campaigns (both must be owned by the caller).

Advance a lead through the pipeline — set its status / pipeline stage and, optionally, a recorded reply, pitch, or notes.

Save a draft email subject and/or body onto one of the user's leads.

Create a reusable pitch template (subject + body templates, optional drafting prompt) owned by the user.

List the caller's sales deals (newest first) together with a weighted pipeline forecast (open/weighted/won totals).

Fetch one of the caller's deals by id with its full activity timeline (notes, calls, meetings, emails, tasks; newest first).

List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts.

What needs attention across my business?

Sales pipeline analytics for the caller: probability-weighted forecast, per-stage $ rollup, win rate (won / decided, by count and by value), average sales-cycle days over won deals, and open-deal aging with a stale count.

The caller's prioritized next-best sales actions: interested leads to convert, open deals gone stale enough to need a follow-up, and overdue tasks — each with a rationale and the exact governed tool to run next (convert_lead_to_deal / log_deal_activity / complete_sales_task) plus its arguments.

Health scores for the caller's OPEN deals: each scored 0-100 on how likely it is to be slipping (healthy >= 70 / watch / at_risk), worst first, with plain-language reasons — days since last logged contact, whether it is past its own expected close date, and how its age compares to the caller's average won-deal cycle.

Create a sales deal owned by the caller.

Update one of the caller's deals — most commonly to ADVANCE its stage (e.g.

Convert an owned outreach lead into a deal and advance the lead into the deal stage of the funnel (never downgrading an already-closed lead).

Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date.

Mark one of the caller's sales tasks/activities done (or reopen it with done=false).

List the caller's invoices (newest first), optionally filtered by status (draft/sent/paid/void).

Fetch one of the caller's invoices by id, including its line items.

Summarize the caller's unpaid invoices by how long they have been past due.

Create a draft invoice owned by the caller for a client, optionally seeded with line items and linked to an existing deal.

Update a draft or sent invoice's header fields (client, terms, due date, tax rate, notes).

Add a billable line item to a draft or sent invoice; totals are recomputed automatically.

Mark a draft invoice as sent (stamps issued_at).

Mark a draft or sent invoice as paid (stamps paid_at).

Void a draft or sent invoice.

Create a draft invoice from one of the caller's deals: one line item for the deal's amount, client_name defaulted from the deal's company/title.

Analyze supported textual accounting records with the pinned deterministic Writeoff engine and create a private, encrypted audit run owned by the caller.

List only the caller's private Accounting-run audit metadata, newest first.

Get one private Accounting run owned by the caller, including its deterministic estimates, disclaimer, engine revision, and audit timestamps.

Permanently delete one private Accounting audit run owned by the caller.

Preview, without writing, how one completed owned Accounting run's WRITEOff work plan would map to stable Meta Council tickets.

Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets.

Preview or idempotently commit an owner-private ticket tree generated from a planning prompt or supplied structured plan.

Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets.

Page through the caller's tickets on the Meta Council board.

Full detail for one owned ticket: description, acceptance criteria, subticket progress, and the recent activity/comment trail.

Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root tickets).

One cross-domain rollup of the caller's own workspace: council sessions (total, last 30 days, by status, tokens), feedback ratings, tickets (open/done), deals (count by stage, open pipeline value) and invoices (count by status, outstanding total, overdue count).

OPERATOR ONLY: cross-owner analytics for the META COUNCIL PLATFORM itself — every account added together, NOT the caller's workspace (use get_workspace_metrics for that).

OPERATOR ONLY: visitor traffic for the META COUNCIL PLATFORM's own website — every visitor added together, NOT the caller's workspace (use get_workspace_metrics for that) and NOT the business rollup (use get_meta_council_platform_metrics for that).

Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary.

List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to.

Fetch one saved ticket view's definition by id: its name, filters, columns, grouping, sort and whether it is shared.

Run a saved ticket view's stored filters against live tickets and return the matching tickets, the view that produced them, and group counts when the view groups.

List your own portfolio snapshots, newest first: the immutable rollups of how your ticket portfolio stood at the moments you captured them.

Fetch one portfolio snapshot by id: its label, schema version, the exact stored rollup payload, its content hash, who recorded it and when.

Compare two of your own portfolio snapshots and return the per-dimension movement between them.

Read the decision and comment thread recorded against one of your portfolio snapshots, oldest first.

Save a named ticket filter, column, grouping and sort bundle so you can reopen it later or share it with a team.

Revise one of YOUR OWN saved views in place, keeping its id and any existing team share.

Retire one of YOUR OWN saved views without destroying it: it drops out of the default listing and execute_saved_view refuses it, but its definition is kept and restore_saved_view brings it back unchanged.

Return one of YOUR OWN archived saved views to the working set with its definition intact.

Share one of YOUR OWN saved views with a single team you belong to.

Make one of YOUR OWN shared saved views private again.

Permanently delete one of YOUR OWN saved views.

Capture an immutable rollup of YOUR OWN ticket portfolio as it stands right now -- totals by status and priority, fixed at this moment and never recomputed.

Record a decision or comment against one of YOUR OWN portfolio snapshots.

Finalize one immutable validation run for an exact owned ticket scenario revision.

Author one Given/When/Then scenario on an owned ticket.

Replace an owned scenario's content, compare-and-swapping on expected_version.

Explain why an owned ticket is not ready to close, using the same readiness check as the browser.

List an owned ticket's scenarios with their exact current revisions, including the current_version and current_definition_hash that ticket_validation_finalize requires.

Record that an owned ticket cannot complete until another owned ticket is done.

Stop an owned ticket from waiting on a prerequisite.

List the prerequisites an owned ticket waits on.

Create a ticket on the caller's board — optionally as a subticket via parent_id.

Update fields on an owned ticket — status moves (each one is auto-logged to the ticket's audit trail), reassignment, priority/effort/action_type recommendations, title/description edits, safe reparenting, opaque session/workflow links, effort points, order, and user-owned external refs.

Retire an owned ticket from the working set, or restore one.

Add a comment to an owned ticket's activity trail.

Claim a ticket to work on: sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged).

Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface.

ADMIN ONLY: list platform-feedback reports — feedback about Meta Council itself, never a tenant's own business data — across all users for triage (requires an ADMIN_EMAILS account; everyone else gets a permission error).

ADMIN ONLY: triage a platform-feedback report — set its status and/or admin notes (requires an ADMIN_EMAILS account; everyone else gets a permission error).

List brand identities owned by the API-key account.

Get one owned brand identity with its voice, value proposition, and guidelines.

List reusable marketing audiences owned by the API-key account.

Get one owned audience definition with pain points and channels.

List owned marketing campaigns.

Get one owned marketing campaign with its brand, audience, channels, and dates.

List owned content assets and immutable revisions; content is never published by this tool.

Get one owned content revision, including its review state and exact content hashes.

List scheduled owned content between optional ISO-8601 boundaries.

Create an owner-private brand identity.

Update fields on one owned brand identity.

Create an owner-private reusable audience definition.

Update fields on one owned audience definition.

Create an owner-private marketing campaign linked only to owned brand/audience ids.

Update one owned marketing campaign.

Create a private draft content asset.

Edit an owned draft.

Create a new owned draft revision from a frozen submitted/approved/rejected revision.

Submit an owned draft for review, freezing that exact revision and content hash.

Approve a submitted owned revision and attest to its exact content hash.

Reject a submitted owned revision with optional reviewer notes.

List consulting clients owned by the API-key account.

Create an account-private consulting client.

Update mutable fields on an owned consulting client.

List consulting engagements owned by the API-key account.

Create an engagement for an owned consulting client.

Update mutable fields on an owned consulting engagement.

Get one owned engagement with its document revisions, milestones, and internal deliverables.

Create a revision-safe proposal or SOW draft on an owned engagement.

Edit an unapproved proposal/SOW revision; approved revisions are immutable.

Idempotently initialize stable engagement milestones.

Update an owned consulting milestone while preserving its stable ref.

Create an internal draft deliverable on an owned engagement.

Edit an internal draft deliverable; review/approval state is separate.

Submit an owned draft deliverable for internal review without publishing it.

Return an unapproved review deliverable to editable draft status.

Approve and lock one exact proposal/SOW revision.

Approve one submitted internal deliverable and record approver evidence.

Create a new custom workflow template the caller owns, so a multi-step pipeline can be built in conversation instead of by hand in the browser.

Replace an existing custom workflow template's definition.

Delete a custom workflow template the caller owns.

Save a standing watch that fires later, on its own: when a count you name crosses a line you set, do the thing you chose.

List the standing watches you have saved, newest first, with what each one watches, what it does, and when it last fired.

Delete one of your standing watches, so it stops firing.

List workflow checkpoints waiting on you, soonest deadline first, with which step is paused and when it runs out.

Answer a waiting checkpoint by request id: approve, reject, or amend.

Export this workspace's own agent-action audit trail as structured events, oldest first, for loading into a SIEM.

Export this account's own data across every table the account owns, as the same JSON envelope the REST route returns.

List the account's overarching project workspaces, separate from feature epics.

Create an owner-private project with intent and goals.

Read project intent, current document IDs/revisions and linked feature epics.

Revision-safely edit project context.

Link an existing owned parentless epic to this project.

Remove one exact project-feature placement, retaining the ticket.

Save the first immutable project brief, PRD, technical specification or decision revision.

Read one exact owned project document revision and its bounded revision history.

Append an immutable document revision using expected_revision and a caller-retained request_id.