KnowMapped

Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account.

От сообществаРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

    Какие данные видит

    Нужен ли аккаунт

    Не нужен: сервер работает без входа

    Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account.

    Список инструментов сервера (10)

    Технические названия из tools/list. Нужны только разработчикам.

    get_knowmapped_update_schemaReturn the authoritative, versioned schema and examples for atomic KnowMapped map patches. Call this before constructing an update instead of guessing operation or field names.
    search_knowmapped_mapsSearch maps available to the connected KnowMapped account. Use this when a user refers to a saved map or wants to find prior concepts; existing ownership and sharing permissions are enforced server-side.
    get_knowmapped_mapRetrieve an authorized map with independent node_offset, edge_offset, and page_size parameters. Canonical IDs are always retained in projected nodes and edges even when include_nodes or include_edges omits id. Use summary for statistics without graph content or compact for token-efficient fields. Search results return copy-safe map references so UUIDs should not be typed manually.
    get_knowmapped_map_adjacencyReturn one concept and its directly connected concepts and relationships without retrieving the full graph. Provide node_id or an exact unique label.
    get_knowmapped_layout_summaryReturn layout bounds and graph statistics without returning graph content.
    preflight_knowmapped_map_creationCheck eligibility and credits, or retain a fully validated graph as a short-lived draft. The exact creation layout field is top-level graph.layout_intent, for example left-to-right. If omitted, Smart is the intent but [0,0] placeholders remain until the map client detects them and applies Smart on first draw; the response reports layout_application=client-first-draw. Complete explicit coordinates are preserved. Fields named layout, layout_type, or strategy are rejected. Drafts do not reserve credits and can be confirmed by draft ID without resending the graph.
    create_knowmapped_mapValidate or create a KnowMapped graph. Specify requested layout only as top-level graph.layout_intent. When omitted, requested_layout and resolved_strategy are smart, but [0,0] placeholders are retained for the map client to lay out on first draw; layout_application is client-first-draw. Complete explicit coordinates are preserved instead. Set validate_only=true to check the exact final graph schema, layout, capacity, links, and credits without creating a map, charging credits, or reserving the idempotency key. For credit-bearing creation, show the quoted charge, then confirm the retained draft only after explicit approval.
    confirm_knowmapped_map_creationTransactionally confirm a preflighted creation by draft ID. Success definitively returns map_id and revision. A failed transaction preserves the draft for retry, and retrying a committed success returns the same result without charging again. Use get_knowmapped_map_creation_result after a timeout or malformed response.
    get_knowmapped_map_creation_resultRecover the definitive state of a map creation without creating a map or charging credits. Provide exactly one draft_id or the original idempotency_key. A succeeded result includes the canonical map ID and revision.
    update_knowmapped_mapValidate or atomically update an editable map with one mixed patch. Accepted operations are update_map, add_node, update_node, remove_node, add_edge, update_edge, remove_edge, replace_edges, and layout_nodes; get_knowmapped_update_schema is the authoritative versioned contract. Use id for identifiers, title for the map title, and layout_nodes with strategy, spacing, groups, and optional flow. Node references accept IDs, earlier temp_id values, or exact unique labels. Edge references accept IDs or semantic source/target/current-relationship matches. validate_only returns a corrected executable normalized_patch, all detectable errors and warnings, layout positions and bounds, a patch summary, publication state, and current revision without changing data. On a stale write, revalidate the same patch at current_revision, then submit the returned normalized_patch.