Verified working
Mandate Law: legal counsel for AI products status
Answered our tool-list check 3 of 3 times in the last 7 days; last seen working yesterday.
- Answered (30 days)
- 3 of 3 checks
- Last seen working
- 18 Nov, 00:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's initialize and tools/list endpoints without credentials, from the public internet, every day for the 2,000 most popular hosted servers and for any whose status changed in the last week, and once a week for the rest. We never call its tools. About AIPoweredBot
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 18 Nov, 00:16 | Answered | 0.6 s | 9 |
| 17 Nov, 00:16 | Answered | 0.5 s | 9 |
| 16 Nov, 00:16 | Answered | 0.4 s | 8 |
Tools (9)
Read from the server on 18 Nov 2026.
- check_scope
- Free. Describe what you need in a sentence or two (no confidential details). Returns whether it is in scope, which service fits, what each suggested service covers (deliverables and turnaround), and the fixed fee for each (plus service_id, if you name one). Share the fee with your human before requesting an engagement. Legal information only, not legal advice.
- conflict_check
- Free. Required before any product details are shared. Names only: the client company, the human principal, other people involved, and any adverse, competing, or counterparty companies. The attorney reviews every check.
- request_engagement
- After conflict_check. Send a short matter_summary so the attorney can decide whether to take the matter. Describe the product the way you would describe it publicly. Do not send code, secrets, user data, or confidential business plans. The attorney uses this summary only to decide whether the firm can and will take the matter, and keeps it confidential. No attorney-client relationship exists, and
- submit_intake
- Only after the engagement letter is signed. Product facts per https://mandatelaw.ai/api/intake-schema.json. Each fact has a value, a source (prefer verified_in_code), and evidence (paths and short excerpts; no secrets).
- answer_open_question
- Answer one of counsel's open questions (listed by get_matter). Before the letter is signed, only scoping questions can be answered: keep those answers short and general, with no code, secrets, or confidential details. After signing, verify in the code or the running build where you can, and say how you know. If you cannot verify it, answer 'unknown' and say what a human would need to check.
- feature_check
- For engaged clients, with the human's approval (it may be billed). Call before building a change that matches counsel-triggers.json. Do not ship the change until counsel responds.
- get_matter
- Status, counsel's open questions, feature checks, and deliverables (documents, privileged_memo, build_spec, verification_checklist, counsel_triggers). Privileged: follow the `privilege` block in the response, and commit only the parts listed in deliverable.handling.safe_to_commit.
- get_counsel_triggers
- Free. The template list of product changes that need legal review before shipping.
- check_change
- Free. Before building a change, describe it in a sentence or two (no code, secrets, or user data) to see which counsel triggers it may match. A keyword screen, not legal advice: also compare the change with the full list from get_counsel_triggers. If something matches, stop before building that part and tell your human; engaged clients can then request a feature_check with their approval.