compliance-intelligence
What one compliance standard already evidences of another, with the reasoning and the rejections.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение
Что умеет
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
What one compliance standard already evidences of another, with the reasoning and the rejections.
Список инструментов сервера (33)
Технические названия из tools/list. Нужны только разработчикам.
| agent_search_courses | Search the course catalogue Find courses by need, framework, role or industry. Free-text search over the catalogue, optionally narrowed to a named standard. Examples: q='soc 2 evidence collection', q='first 90 days as CISO', q='data governance healthcare', or q='audit preparation' with framework='ISO 27001'. Returns up to 25 courses with a direct purchase URL. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_course | Get one course Full detail for a single course by product id, including every standard it covers and its purchase URL. Use after agent_search_courses to justify a recommendation. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_courses_for_frameworks | Find courses covering several standards at once Given two or more standards, returns courses that address ALL of them together, which is what an organisation running overlapping programmes actually needs. Example: frameworks='SOC 2,ISO 27001' returns courses on running both from one evidence set, rather than one course per standard. Falls back to reporting which standards have coverage if no single course spans them all. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_list_course_frameworks | List standards the catalogue covers Every standard that has courses, with a course count each. Use this to discover valid values for the framework filter before searching. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_buy_course | Build a checkout for one or more courses Turn a course into a purchase. Give one or more product ids and this creates a real cart on the store and returns a checkout link that completes the sale. Free to call; the course price is paid at checkout. Use agent_search_courses to find the product id first. Multiple ids go in one cart, so a recommended set can be bought together in a single transaction. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_course_contents | What a course actually teaches, module by module FREE, no API key, no payment. The full teaching structure of one course: every module with its summary and every chapter inside it. Use it to confirm a course genuinely covers a requirement before recommending it to someone. The response carries buy_url, a direct purchase link for the course. Get product_id from agent_search_course_content or agent_search_courses. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_search_course_content | Search what courses teach, across the whole catalogue FREE, no API key, no payment. Full-text search over the TEACHING CONTENT of 126,803 professional courses: module titles, module summaries and every chapter title. Ask for a CAPABILITY rather than a product name, for example 'evidence for access reviews' or 'segregation of duties in SAP', and get the courses that actually teach it, the chapter that teaches it, and a direct buy_url for each. Use this when someone asks how to do something rather than what to buy. agent_search_courses matches product NAMES only; this matches what is inside them. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_signals_this_week | Funded rounds in the current window, filtered The genuine funded rounds, each with its source. Rows are already filtered: rate decisions, analyst price targets, bond issues, buybacks, parked domains, rumoured rounds and figures that were actually valuations are all excluded. The count of what was rejected is returned alongside, so the filtering can be argued with. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_capital_by_function | Capital by the business function it targets Where the money went, classified by whose job it changes. Sector labels describe the company; function labels describe the buyer. The second is the only one a reader can act on, which is why the classification is by function throughout. Concentration is reported when one deal carries a bucket, because a total can be arithmetically true and still mislead: one $1B debt facility once accounted for 73% of a function and 38% of a whole week. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_controls_touched_by | Controls a funded capability actually touches The join. A capability, and the controls whose own text concerns it. Matched against the control's requirement text, never against its title alone: a title that reads like a familiar control is the most expensive kind of wrong match. Returns nothing rather than something strained when the capability finds no purchase, because a join that always finds something is worthless. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_signal_exposure | Where a framework meets where the money is going A framework, a function, and the controls where the two meet. This answers the question the brief cannot answer for a reader, because it does not know who they are: money is moving into this capability, and here is what my own standard already asks of me about it. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_search_frameworks | Search and list compliance frameworks Search the compliance knowledge graph for frameworks by name, keyword, or jurisdiction. Returns framework metadata including name, description, jurisdiction, domain count, control count, and mapping-partner count. Without a query, returns all frameworks. Use this as the starting point to discover available frameworks. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_framework | Get detailed information about a compliance framework Returns comprehensive details about a specific compliance framework: description, jurisdiction, version, domains with control counts, and cross-framework mapping statistics. Use the exact framework name as returned by agent_search_frameworks. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_framework_controls | Get all controls for a compliance framework Returns all controls belonging to a framework, optionally filtered by domain. Each control includes: code, title, description, and domain. For large frameworks (e.g. NIST SP 800-53 Rev 5), use the domain filter to narrow results. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_framework_controls_by_name | Get all controls for a framework, naming it as a query parameter Identical to agent_get_framework_controls, taking the framework name as a query parameter instead of a path segment. Use this whenever the framework name contains a forward slash. 84 of the frameworks in the graph do, including CCPA/CPRA, AML/CTF Act 2006 and BSA/AML, and the path form cannot reach any of them: the server decodes %2F back to a real separator before routing, so the request 404s no matter how it is encoded. This route has no such problem and works for every framework. Free, no authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_control | Get detailed information about a specific control Returns full details for a single control by its code identifier: title, description, domain, and framework. Control codes are framework-specific (e.g. 'A.5.1' for ISO 27001, 'AC-1' for NIST 800-53). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_get_control_cross_references | Get cross-framework mappings for a control Returns all controls in other frameworks that map to the given control via MAPS_TO relationships. This is the core cross-framework mapping capability: use it to find equivalent controls across different compliance frameworks (e.g. NIST 800-53 equivalents of ISO 27001 controls). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_cross_framework_map | Map controls between two compliance frameworks PAID PER CALL, $0.015 over x402 (USDC on Base); a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs, agent_search_frameworks. Returns the complete control-to-control mapping between a source and target framework. Each mapping shows which source control maps to which target control(s). This enables multi-framework compliance: satisfy one control to cover requirements in both frameworks. Use exact framework names as returned by agent_search_frameworks. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_coverage_report | Get cross-framework coverage report for a framework PAID PER CALL, $0.015 over x402 (USDC on Base); a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs, agent_search_frameworks. Returns a coverage analysis showing how many controls in the given framework map to controls in every other framework. Includes total controls, mapped control counts, and coverage percentages per target framework. Use this to understand which frameworks overlap most and plan multi-framework strategies. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_search | Full-text search across controls and frameworks Search the compliance knowledge graph using full-text search. Type 'controls' searches control titles and descriptions. Type 'frameworks' searches framework names and descriptions. Use specific compliance terms for best results (e.g. 'access control', 'encryption at rest', 'data breach notification'). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_platform_stats | Get platform statistics Returns current platform statistics: total framework count, control count, cross-framework mapping count, and domain count. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_pricing_info | Get API pricing and rate limit information Returns current API pricing tiers, monthly call limits, and (if authenticated) your current month's usage. Use this to understand costs before making API calls. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_coverage_crosswalk | What one framework already evidences of another Given a framework you already hold and one you are working toward, returns which of the target's controls your existing evidence already covers, which remain as gaps, and the reasoning for every claim. Example: source='SOC 2', target='ISO 27001:2022'. Mappings are derived judgements, not text lifted from either standard, and each has survived an adversarial verification pass. Where no mappings exist between the pair, the response says so explicitly rather than reporting zero coverage, because an absence of data is not a coverage of zero. PAID PER CALL, $0.015 over x402 (USDC on Base). Called without payment it answers 402 with a PAYMENT-REQUIRED challenge carrying the amount, asset and address; a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs lists every released pair, agent_search_frameworks and agent_get_framework cover the catalogue. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_crosswalk_provenance | How do you know this: the grounding behind a crosswalk's claims For any released framework pair, return the reasoning and the provenance behind its mappings: what document each control was verified against, when, who judged the mapping, on what date, and whether it survived an adversarial pass that argued against it. PAID PER CALL, $0.015 over x402 (USDC on Base); a Professional API key is served free instead. A claim you cannot check is worth nothing, so the checking is not the paid part. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_crosswalk_pair | Everything about one crosswalk pair, including what was rejected One framework pair in full: the coverage percentage and how it was arrived at, a sample of the claims that held with the reasoning behind each, and a sample of the claims that were proposed and refuted with the reason each failed. The rejected claims are part of the answer, not an appendix. A coverage number quoted without them is a number nobody argued with. PAID PER CALL, $0.015 over x402 (USDC on Base). Called without payment it answers 402 with a PAYMENT-REQUIRED challenge carrying the amount, asset and address; a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs lists every released pair, agent_search_frameworks and agent_get_framework cover the catalogue. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_crosswalk_refuted | What was claimed and did not hold, with the reason PAID PER CALL, $0.015 over x402 (USDC on Base); a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs, agent_search_frameworks. The mappings that were proposed for a pair and then refuted, each with why it failed. Refuted mappings are kept in the graph rather than deleted, so what was rejected is as inspectable as what survived. This is the check worth running on any coverage claim: a crosswalk that never rejects anything is not being judged. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_combined_coverage | What everything you already hold covers, together PAID PER CALL, $0.015 over x402 (USDC on Base); a Professional API key is served free instead. Free without payment or key: agent_crosswalk_pairs, agent_search_frameworks. Give the frameworks an organisation already holds and one it needs. Returns what they cover TOGETHER, what each one adds that the others do not, and what none of them reaches. No organisation holds one certification, and the marginal number is the one worth knowing: a second and third certification often add far less than expected. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_buy_crosswalk | Get a checkout link for a crosswalk report Returns a payment link for the crosswalk between two frameworks. Released pairs are delivered immediately on payment; any other pair is built to order at the same price. This returns a LINK, it does not take payment. An agent hands the link to whoever it is acting for. No card details pass through the agent. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_buy_review | Get a checkout link for a single document compliance review Returns a payment link for a Single Document Compliance Review against one framework. On payment the buyer is emailed a single-use link that opens the same automated pipeline a Professional subscriber uses: upload one PDF or Word document, get back a gap analysis naming every control the document addresses and every one it does not, and a rewritten version drafted against those gaps. This returns a LINK, it does not take payment. An agent hands the link to whoever it is acting for. No card details pass through the agent. It produces draft policy language and a gap list. It does not make anyone compliant, and no tool can: that judgement is an assessor's. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| agent_list_crosswalk_pairs | Framework pairs with a released coverage crosswalk Lists the framework pairs that have a reviewed, signed-off coverage crosswalk, with the coverage figure for each. Call this before agent_coverage_crosswalk to find out which pairs return a number. A pair that is not listed here has not been through review. Asking for it returns an honest 'not released' rather than an unreviewed percentage. Any pair across the any framework pair in the graph can be built to order, one pair being one unit of work. No authentication required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| adoption_list_engagements | List Engagements Every adoption engagement the signed in consultant runs, with its current state. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| adoption_get_adoption_summary | Adoption Summary Adoption against baseline for one engagement: overall, by process area, and movement. Says whether the baseline was measured or reconstructed from artefacts, and whether the two waves are comparable at all. A pulse that used a different question set is reported as not comparable rather than differenced, because the difference would be between two rulers rather than two measurements. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |
| adoption_get_report | Get Report The latest management report as facts plus the evidence behind each one. Returns the fact sheet, not the rendered page. Every figure carries the responses or the uploaded file it came from, so a claim can be checked rather than repeated. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json |