Saltar al contenido principal

Conectar un agente de IA a tu cuenta

El agente con el que ya trabajas puede gestionar tus colaboraciones sin abrir el navegador.

Un comando y listo

El comando abre 1lev1 en tu navegador, apruebas la conexión y la clave se escribe automáticamente en cada agente que tengas instalado — junto con la skill.

npx 1lev1-mcp

Reinicia el agente después para que cargue la nueva configuración.

Desde el móvil y el navegador — sin terminal

La app de Claude, claude.ai y Claude Code en el navegador se conectan mediante un connector: pegas una dirección, apruebas en el navegador y ya está. No hay clave que copiar ni archivo de configuración que editar.

Añadir a Claude con un clic
  1. Pulsa el botón. claude.ai se abre en el diálogo de añadir, con el nombre y la dirección ya rellenados.
  2. Pulsa Add y luego Connect. Se abre una página de 1lev1: inicia sesión y aprueba la conexión.
  3. Listo. Una sola conexión cubre el chat en el ordenador, la app del móvil y Claude Code en el navegador.

¿El botón no se abrió? Ve a Ajustes → Connectors → Add custom connector, ponle un nombre — 1lev1, por ejemplo — y pega la dirección del servidor de abajo.

Dirección del servidor

https://api.1lev1.com/api/mcp

La conexión crea una clave de API normal en tu cuenta. Aparece en la página de claves de API y se revoca desde allí, igual que una clave creada desde la terminal.

Claude Code — mediante el plugin

Si trabajas en Claude Code puedes instalar la skill desde el marketplace y luego conectar tu cuenta con el comando de arriba.

/plugin marketplace add Avi-ADAM/1lev1-agent
/plugin install 1lev1@1lev1

El plugin aporta el conocimiento; el comando de conexión aporta el acceso. Hacen falta los dos.

Qué puedes pedirle

  • ¿En qué se supone que debo trabajar hoy?
  • Inicia el temporizador de la misión del logo.
  • Ayer trabajé tres horas en el diseño — regístralo.
  • ¿Cuántas horas llevo acumuladas en esta colaboración?
  • Convierte este repositorio en una colaboración entre los tres.
  • ¿Qué está esperando mi aprobación?

Lo que el agente no hará por ti

1lev1 se basa en el consentimiento, así que el agente nunca ejecuta un acto que afecte a otra persona. En su lugar prepara el formulario y te envía a aprobarlo en el sitio.

  • No vota ni firma un reparto de beneficios en tu lugar.
  • No acepta ofertas ni cambia la situación de otro miembro en una colaboración.
  • No puede ver los datos de ningún otro usuario — la clave está ligada sólo a tu cuenta.
  • Crear misiones y tareas para otras personas está desactivado por defecto y requiere un permiso explícito.

Qué es esto realmente

MCP es un protocolo abierto que permite a un agente de IA conectarse a servicios externos. El servidor MCP de 1lev1 da a tu agente acceso a tus misiones, temporizadores y colaboraciones — y sólo a los tuyos. La skill que se instala junto a él le enseña cómo funciona la plataforma: qué es una rikma, por qué las horas registradas son propiedad y qué no debe hacer jamás en nombre de otra persona.

Agentes compatibles

El comando detecta lo que realmente tienes instalado y escribe sólo ahí: Claude Code, Claude Desktop, Cursor, Windsurf, Cline, Roo Code, Continue, Antigravity y VS Code. No toca ningún archivo de configuración que no pueda leer, y guarda una copia de seguridad antes de cada cambio.

ChatGPT, Gemini y otros agentes

El servidor habla MCP estándar, así que no es exclusivo de Claude. Lo que funciona hoy:

  • ChatGPT — activa el Developer mode en los ajustes, añade un connector con la misma dirección del servidor y apruébalo en el navegador. Solo en planes de pago.
  • Gemini CLI y Antigravity — el comando de conexión de arriba escribe en ellos directamente, como en cualquier otro editor.
  • Gemini Enterprise — un administrador añade un servidor MCP propio en Connected apps. Ese formulario pide client id y secret manuales: escríbenos y los emitimos para la dirección de retorno de tu organización.
  • Codex CLI — se añade a mano en ~/.codex/config.toml, con la clave en una variable de entorno y no en el propio archivo.
  • n8n, Zapier o un agente escrito por ti — cualquier cliente MCP que hable Streamable HTTP con cabecera Authorization funciona contra la misma dirección.
[mcp_servers.lev1]
url = "https://api.1lev1.com/api/mcp"
bearer_token_env_var = "LEV1_API_KEY"

La app de Gemini para consumidores todavía no permite añadir un servidor MCP por tu cuenta: allí las conexiones se abren solo mediante acuerdos con Google.

Configuración manual

Si tu agente no está en la lista, puedes añadir el servidor a mano. Obtén la clave con el comando de arriba.

Dirección del servidor

https://api.1lev1.com/api/mcp
{
  "mcpServers": {
    "1lev1-mcp": {
      "type": "http",
      "url": "https://api.1lev1.com/api/mcp",
      "headers": { "Authorization": "Bearer 1lev1_..." }
    }
  }
}

Seguridad y desconexión

  • La clave es una contraseña a todos los efectos. No la compartas ni la subas a git.
  • Volver a aprobar desde el sitio reemplaza la clave anterior y revoca el acceso antiguo.

Para desconectarte del todo, este comando elimina el servidor y la skill de todos los agentes.

npx 1lev1-mcp remove

Ese comando sólo limpia tus configuraciones locales — la clave sigue siendo válida. Para invalidarla, vuelve a ejecutar el comando de conexión y aprueba: reemplaza la clave anterior.

Para asistentes de IA

Referencia de herramientas

Todas las herramientas que el conector da a una cuenta con sesión iniciada, tal como las devuelve el propio servidor - así que esta lista es siempre la que recibe tu asistente. Las descripciones son lo que lee el asistente, por eso siguen en inglés.

Cómo trata el conector tu información

Sin cuenta

Responden antes de que nadie inicie sesión. prepareSignup guarda un borrador de registro para quien aún no tiene cuenta - su nombre, su correo y lo que busca - que no compromete a nadie hasta que esa persona lo firme, y caduca a los 14 días. Cualquier otra herramienta pide iniciar sesión primero.

getPlatformInfo

About 1lev1
  • Solo lectura

Get general information about the 1lev1 platform, its goals, and features.

Entradas

Sin entradas.

prepareSignup

Prepare a signup
  • Cambia datos

Prepare a 1lev1 signup for a person who has NO 1lev1 account yet, so joining is one screen - the agreement prefilled with their name, email and countries, and the password on the same screen. Use it only when the person's own request is what 1lev1 does: finding partners for their work, turning a business or an idea into a partnership where the work, resources and money each partner brings become a share, or having something made or arranged by partners through the concierge. Do not bring it up in any other conversation. Before calling, tell the person what will be sent and get their go-ahead; pass only the name and email they gave you for this signup (ask for them - never take them from memory or earlier chats). intent: "business" (add their business so the concierge finds and orders from it), "partnership" (see an existing partnership on 1lev1), "idea" (break an idea down and recruit partners) - for these three send the rikma blueprint you built (the same shape as proposeRikmaBlueprint takes: fields, products first, missions, resources, partners) and you get TWO links to share with the person: `previewUrl` (the rich public rikma page, safe to share with anyone) and `manageUrl` (behind-the-scenes studio where they can edit the rikma, add/remove missions, products and resources, adjust hours +/-, watch shares update live, and sign up & create from there), plus `signupUrl` (direct 1-screen prefilled signup); "join" (join rikmas - pass aboutText: who they are, what they do); "order" (they want something made or arranged - pass wishText). You cannot sign, set a password or confirm the email for them, and nothing is created until they do. Always give them BOTH `previewUrl` (public rikma page) and `manageUrl` (behind-the-scenes control & signup) when preparing a rikma, or `signupUrl` otherwise (valid 24h). After they confirm their email they land straight in what you prepared.

Entradas
name string obligatorio
The name the person gave you to sign up with.
email string obligatorio
The email the person gave you to sign up with - the confirmation goes there.
countries string[] opcional
Country names in English, e.g. ["Israel"].
lang "he" | "en" | "ar" | "ru" | "es" opcional
intent "join" | "business" | "partnership" | "idea" | "order" obligatorio
aboutText string opcional
wishText string opcional
blueprint object opcional

Lectura

Solo lee. Devuelve lo que tú mismo verías en el sitio.

findUserProjectsTool

Find my rikmas
  • Solo lectura

Find the projects (rikmot) the current user belongs to, newest first, with their creation time. Use this when the user mentions a project by name, wants to navigate to one, or just created one. Results are paginated: when hasMore is true, call again with offset=nextOffset.

Entradas
userId string opcional
User id to list projects for. Omit to use the authenticated caller.
query string opcional
Optional search query to filter projects by name (case-insensitive substring).
limit integer opcional
Page size, default 50.
offset integer opcional
How many results to skip, default 0.

getProjectDetailsTool

Get rikma details
  • Solo lectura

Get the facts about one rikma (project): name, public description, values, links (website, GitHub, Drive, social), members, roles, open missions, missions in progress (and who holds them), open and in-progress resources, and products. Call this before planning or writing anything in a rikma - it is cheap and returns facts, unlike scanProjectDirectionsTool. For a rikma the user is not a member of, only the public face is returned (isMember:false).

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.

listProjectResourcesTool

List rikma resources
  • Solo lectura
  • Solo miembros de la rikma

List what a rikma already has and needs: its links (live website, repo, Drive, social), resources in progress (equipment, money, services someone provides) and open resources it is looking for, plus its products. Use it to check whether a rikma already has a website/repo before suggesting one. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.

getProjectStatsTool

Get rikma stats
  • Solo lectura
  • Solo miembros de la rikma

Get the pulse of one rikma as numbers: members, open missions, missions in progress, open resources, open decisions (votes), active timers, missions finished and hours logged in the last N days, and when anything last happened. Use it to judge whether a rikma is active before planning. Members only; no per-member financial data.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.
days integer opcional
Window for the "recent" numbers, default 30.

getProjectMembersTool

List rikma members
  • Solo lectura
  • Solo miembros de la rikma

List the people (members) and roles (tafkidim) of a project. Use this to resolve a task assignee - a person or a role - to its ID before calling createTaskTool. For a task with no specific person, pick the roles that fit it here and pass their IDs as tafkidims.

Entradas
projectId string obligatorio
ID of the project
query string opcional
Optional text to filter people or roles by name

getMemberMissionsTool

List a member's missions
  • Solo lectura
  • Solo miembros de la rikma

List a project member's in-progress missions. A task is linked to a mission-in-progress the assignee performs, so call this after choosing the assignee (a person) to pick the missionId to pass to createTaskTool. If no mission in progress covers the work, it is not a task: prepare a mission with prepareMissionTool instead.

Entradas
projectId string obligatorio
ID of the project
userId string obligatorio
ID of the member (assignee) whose in-progress missions to list

getMissionDetailsTool

Get mission details
  • Solo lectura
  • Solo miembros de la rikma

Get detailed information about a specific mission including tasks, timeline, and current status

Entradas
missionId string obligatorio
Mission ID to get details for

listUserMissionsTool

List my missions
  • Solo lectura

List user missions with various filtering options

Entradas
filter "all" | "active" | "completed" | "startable" | "stoppable" | "overdue" opcional
Filter missions by status
projectId string opcional
Filter by specific project ID (numeric)
projectName string opcional
Filter by project name
missionName string opcional
Search for missions by name (partial match)
limit number opcional
Maximum number of missions to return

findMissionTool

Find one of my missions
  • Solo lectura

Find one of YOUR missions in progress (missions you already hold) by its name, to get its id for a timer or details. It does not search openings: to discover open missions and resources use searchCatalogTool, and for what fits this user use listMyMatchesTool.

Entradas
missionName string obligatorio
The name of the mission to find.

getActiveTimersTool

Get running timers
  • Solo lectura

Get all currently active timers for the user

Entradas
includeDetails boolean opcional
Include detailed timer information

getMissionStatsTool

Get mission stats
  • Solo lectura

Get statistics about user missions including counts by status, time spent, etc.

Entradas
projectId string opcional
Get stats for specific project only

searchCatalogTool

Search the catalog
  • Solo lectura

Search what the platform already offers publicly: products for sale, open missions (work looking for someone) and open resources (equipment, money, services a rikma needs). Use it before opening a new wish or mission - somebody may already do this. Public data only.

Entradas
query string obligatorio
Free text; matched against names, descriptions and rikma names.
kinds "products" | "missions" | "resources"[] opcional
Which directories to search. Default: all three.
limit integer opcional
Maximum rows per kind, default 10.

searchRikmasTool

Search rikmas
  • Solo lectura

Search the public directory of rikmas (partnerships) by text - name, public description, city - with how many members each has and how many open missions, open resources and products. For finding a rikma to join or work with; getProjectDetailsTool then shows one rikma's public face. Public data only.

Entradas
query string opcional
Free text. Empty: the newest rikmas.
limit integer opcional
Maximum rows, default 10.

listMyMatchesTool

List my matches
  • Solo lectura

Open missions the platform has already matched to THIS user (from their skills, roles and ways of working), best first, with what they matched on, the hours and hourly rate offered, and the rikma. Each row carries the public page where the person can read the mission and offer to take it - applying is their own step there.

Entradas
limit integer opcional
Maximum rows, default 10.

getMyStakeTool

Get my share in a rikma
  • Solo lectura
  • Solo miembros de la rikma

The user's share in one of their rikmas, and every member's share, exactly as the rikma's split page computes them: value from finished missions (approved hours x rate), resources the rikma received, and confirmed stipend payments - with the missions and resources behind each share. Members only. Read-only; it shows no sales or profit-split figures.

Entradas
projectId string obligatorio
The rikma id (findUserProjectsTool).

listMyApplicationsTool

List my applications
  • Solo lectura

The user's own open candidacies: missions they offered to take and resources they offered to bring. For each, the terms on the table (after any counter-proposal), who in the rikma has signed and who has not yet, and the deadline - when it passes with no counter, silence approves the candidacy. Read-only. To withdraw, discuss or counter, give the user `url`.

Entradas

Sin entradas.

getDecisionTool

Get a decision
  • Solo lectura
  • Solo miembros de la rikma

One decision (vote) of a rikma as structure: what it proposes, the round on the table, who has signed it and who has not yet, and the deadline - when the deadline passes with no counter-proposal, silence approves it. Members only; a sale-holder claim is visible only to its two parties. Read-only: it never votes. To sign, discuss or counter, give the user `url`. The decision ids come from getMyUpdatesTool.

Entradas
projectId string obligatorio
The rikma id.
decisionId string obligatorio
The decision id.

getRikmaLedgerTool

Get rikma sales and splits
  • Solo lectura
  • Solo miembros de la rikma

A rikma's money, read-only: its sales (income) and who holds each, the profit splits still open with their transfers and who has signed, the transfers of signed splits still waiting for the receiver to confirm (transfersToConfirm), and the user's own position - their share, what they hold, and what they would pass on or receive if the rikma split now. Only sales whose holder agreed are counted; a claim still waiting for the holder appears only as a count. Members only. It never proposes, confirms or moves money: give the user `salesUrl` for that.

Entradas
projectId string obligatorio
The rikma id (findUserProjectsTool).

findPartnersTool

Find partners by skill
  • Solo lectura

Find people on 1lev1 by a skill or a role (e.g. "video editing", "designer"), to partner with. Returns how many people match, and names (username, skills, roles, public profile page) only of those who chose to be findable by agents - never contact details. To reach everyone who matches, prepare an open mission (prepareMissionTool): once published, the platform suggests it to them in their own mission suggestions. It contacts nobody itself.

Entradas
query string obligatorio
A skill or role, a word or two.
limit integer opcional
Maximum named people, default 10.

searchContentTool

Search my rikmas
  • Solo lectura

Search inside the rikmas the caller belongs to: rikma names and descriptions, open missions, missions in progress, acts, open and in-progress resources, and products. Use it to find something when the rikma is not known - "where was that task about the logo". For public listings of other rikmas use searchCatalogTool instead.

Entradas
query string obligatorio
Free text; matched against names and descriptions.
limit integer opcional
Maximum rows per kind, default 10.

listMyWishesTool

List my wishes
  • Solo lectura

List the caller's own wishes (concierge requests): status, coverage, and how many missions and resources each one still needs. Use it to answer "what did I ask for" and to pick the wish a follow-up is about.

Entradas

Sin entradas.

getWishDetailsTool

Get wish details
  • Solo lectura

Get one wish (concierge request): what it needs broken into missions and resources, its coverage, and the proposals on it. Full detail for the wish owner and for anyone who proposed on it; others see only the public card of an open wish. Accepting or declining a proposal is never done here - open the returned URL and let the person decide.

Entradas
wishId string obligatorio
Wish (ratson) id, from listMyWishes or a /concierge or /wish URL.

listMyWishOffersTool

List offers on my wishes
  • Solo lectura

The supplier side of the concierge: every proposal the caller is the proposer of - what someone asked them to provide and what they offered, with its status. Use it to answer "who wants something from me". Responding to one happens on its page, not here.

Entradas

Sin entradas.

getMyUpdatesTool

What's waiting for me
  • Solo lectura

What waits for the user and what is new for them - across their rikmas, their wishes (concierge) and their deals. Use it for "what's new today", "what is waiting for me", "what do I need to answer", "what is happening in rikma X". Returns `waiting`: each item is ONE ready sentence in the user's language, with its figures, where it is, its deadline (when `silenceApproves` is true, no answer by the deadline approves it automatically - always say so), and a `link` where the user answers it. Relay the sentences, most urgent first; do not reword figures. Also returns `work` (their missions, missions about to go dormant, open/overdue tasks), `whatsNew` (counts of new missions/resources/products/sales in their rikmas since yesterday) and `suggestions` (open matches for them). `unavailable` names parts that could not be read - say they could not be checked rather than calling them empty. Read-only: approving, countering or discussing happens on the site, by the user.

Entradas
projectId string opcional
Only this rikma (its id, e.g. from findUserProjectsTool).
rikma string opcional
Only rikmas whose name contains this text - use when the user names a rikma and you have no id.
lang "he" | "en" | "ar" | "ru" | "es" opcional
The language to word the sentences in. Default: the user's language.
limit integer opcional
How many waiting items at most (default 20).

getAssistantTool

Get a draft list
  • Solo lectura

Read the person's current draft list on 1lev1 - a rikma blueprint (kind 'rikma'), or later their profile or a wish - with its rows, their keys and status, the version, and what was changed recently (also from the site). Call it before setAssistantItems when you are not sure you have the latest version.

Entradas
kind "rikma" | "profile" | "wish" opcional
Latest session of this kind.
sessionId string opcional

listMyConversationsTool

List my conversations
  • Solo lectura

List the conversations (forums) the caller takes part in - one per mission, act, decision, profit split or wish proposal they are involved in, newest first, with the last message. Use it to find the forumId of the thread a request is about.

Entradas
projectId string opcional
Only conversations of this rikma.
limit integer opcional
Maximum rows, default 25.

readConversationTool

Read a conversation
  • Solo lectura

Read one conversation (forum) the caller takes part in: its messages, newest last, with who wrote each. Use it before answering in a thread, so the reply fits what was already said.

Entradas
forumId string obligatorio
Forum id, from listMyConversations.
limit integer opcional
How many of the most recent messages, default 30.

getSitePagesTool

List site pages
  • Solo lectura

Get a structured list of available pages on the 1lev1.com site, useful for navigation.

Entradas

Sin entradas.

listRikmaProcessesTool

List rikma processes
  • Solo lectura
  • Solo miembros de la rikma

List a rikma's processes: the open-ended threads it is running - an approach to a partner, a launch, a funding attempt - each with its conversation and the open missions, resources and other objects that have formed out of it. Use it to see what is already in motion before starting something new. Members only.

Entradas
projectId string obligatorio
Rikma (project) id.

listRikmaProductsTool

List rikma products
  • Solo lectura
  • Solo miembros de la rikma

List the products (Matanot) of one rikma for the merchant: name, price, pricing mode, status, archived, kind, quantity (-1 = unlimited), lowStockAt, stockTotal, hasVariants, and each variant (sku, price, quant, active, axisKey). This is the seller view used by the sales/manage tabs (moachShopProducts) — not the public catalog. Members only. Call it first to see what you have on the shelf before creating, editing stock or checking orders.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.
includeArchived boolean opcional
Also return archived products. Default false.
kindOf string opcional
Filter by kindOf: total, monthly, yearly, daily, unlimited.
search string opcional
Free-text filter over name (case-insensitive, in-memory).

getRikmaProductTool

Get rikma product
  • Solo lectura
  • Solo miembros de la rikma

Get one product of the rikma in full merchant detail: its base row (price, quant, pricingMode, status_of_voting, lifecycle, archived, hideFromDiscovery, lowStockAt, unit, minOrder, maxOrder, leadTimeHours, externalKey, pricing fields), its gallery and delivery options, its option axes (product-option), every variant (sku, axisKey, optionValues, price, quant, active, position, externalKey), categories, and computed inventory (effectiveStock, isLowStock, lowVariants). Members only. Use it to verify a product before editing stock, pricing or variants.

Entradas
projectId string obligatorio
Rikma (project) id.
productId string obligatorio
Matanot id (from listRikmaProducts).
includeArchived boolean opcional
Allow a row that is archived lifecycle=false. Default true for a direct get.

getShopInventoryTool

Get shop inventory
  • Solo lectura
  • Solo miembros de la rikma

Inventory overview for a rikma: how many products are active, archived, low, out of stock, and per-variant stock. Also loads the waiting orders and any oversold (short) units so the seller knows what the shelf does not cover. Members only. This is what the Stock tab of sales/manage shows, as facts an agent can act on.

Entradas
projectId string obligatorio
Rikma id.
includeArchived boolean opcional
Count archived products in the totals. Default false.

listRikmaProductOptionsTool

List product options
  • Solo lectura
  • Solo miembros de la rikma

List the option vocabulary (product-option) of one rikma: axes like size / colour, each with its values (value, label, hex, image). These are the axes a product declares it uses (product.options) and the `axisKey` of a variant is built from them. Members only. Use it to see what size M really is before writing a variant that claims it.

Entradas
projectId string obligatorio
Rikma id.

listRikmaProductVariantsTool

List product variants
  • Solo lectura
  • Solo miembros de la rikma

List the variant rows (product-variant, the SKU) of products of one rikma — price, compareAtPrice, quant (-1 unlimited), active, position, sku, name, optionValues and axisKey, with productId and pics. This is the truth the checkout consults. Members only.

Entradas
projectId string obligatorio
Rikma id.
productIds string[] obligatorio
Matanot ids to pull variants for (from listRikmaProducts).

listRikmaOrdersTool

List rikma orders
  • Solo lectura
  • Solo miembros de la rikma

List the paid orders the storefront reported (POST /orders, §3.3) for one rikma: ref, displayNumber, status (paid/shipped/fulfilled/cancelled), oversold, total, currency, buyer (name/email/phone — sensitive), delivery preference and address, payment ref/method, holder, paidAt/shippedAt/fulfilledAt, lines (productId/variantId, nameSnapshot, optionLabelSnapshot, skuSnapshot, quantity, unitPrice, lineTotal) and sales. Members only — buyer contact leaves the server only inside a members-only response (§5.6) and is never copied to a webhook.

Entradas
projectId string obligatorio
Rikma id.
status "paid" | "shipped" | "fulfilled" | "cancelled" opcional
Filter to one lifecycle state.
oversoldOnly boolean opcional
Only orders whose stock ran short.
limit integer opcional
Return at most this many, default 50.

getRikmaOrderTool

Get rikma order
  • Solo lectura
  • Solo miembros de la rikma

Get one order of the rikma by its ref (`<rikmaId>:<externalId>`, as POST /orders answered). Returns the same enriched order as the list, plus the holder and the note the rikma sees. Members only — buyer contact is members-only.

Entradas
projectId string obligatorio
Rikma id.
orderRef string obligatorio
The order ref, e.g. "57:pi_3Q8x…" — or an orderId (the tool tries both).

listRikmaLeadsTool

List rikma leads
  • Solo lectura
  • Solo miembros de la rikma

List the enquiries (leads) a rikma is working on before money: people who wrote in, and concierge wish proposals the rikma is a candidate on. Each row: kind, id, name, organization, source, stage (new / contacted / talking / offered / paused), who owns it (ownerId — null means nobody took it yet), lastAt, followUpAt, nextAction and attention (unanswered / followUpDue / stale — why it needs someone). Sorted: needs attention first, then whatever waited longest. No phone or email here — open one lead for that. Members only.

Entradas
projectId string obligatorio
Rikma id, from findUserProjectsTool.
view "open" | "attention" | "paused" | "mine" | "nobody" opcional
'open' (default): everything in play · 'attention': needs someone now · 'paused': not now · 'mine' · 'nobody': nobody took it
limit integer opcional
At most this many rows, default 30.

getLeadTool

Get a lead
  • Solo lectura
  • Solo miembros de la rikma

Open one lead of a rikma: who they are and how to reach them (phone and email — sensitive, for the member to act on, never to be copied anywhere else), what they asked, its stage, owner, next step, day to get back, linked orders, and its log (most recent first: calls, messages, meetings, notes, status changes). Members only.

Entradas
projectId string obligatorio
Rikma id.
leadId string obligatorio
Lead id, from listRikmaLeadsTool (rows of kind "lead").
logLimit integer opcional
How many log entries, default 20.

getShippingConfigTool

Get shipping setup
  • Solo lectura
  • Solo miembros de la rikma

Describe how a rikma delivers what it sells: whether shipping is set up, the currency, handling days, the lowest free-delivery threshold, each zone (countries, districts, cities, postal prefixes) with its methods (fee, freeOver, minSubtotal, ETA days, dispatch days), the pickup points, and per-product rules (which products are pickup/digital only). Members only. For "how much is delivery of X to <city>?" use quoteShipping — it prices a real cart.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.

quoteShippingTool

Quote shipping
  • Solo lectura
  • Solo miembros de la rikma

Price delivery of a cart from one rikma to an address — "how much is delivery to Haifa?". Give the products (and variant when the product has variants) with quantities, and the address (city is enough inside Israel; the district is resolved from it). Unit prices are read from the rikma's own catalog, so free-delivery thresholds apply as at checkout. Returns every option (delivery methods, pickup points, digital, "contact the seller") with fee, whether it is free, how much more makes it free, ETA and next dispatch day, plus why delivery is unavailable (outsideZones, noDeliveryProducts, needsAddress, weightUnknown). Members only; read-only — nothing is ordered.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool.
items object[] obligatorio
What is being sent.
address object opcional
Where it goes. Omit to see pickup/digital options and which methods would need an address.

listRikmaCategoriesTool

List product categories
  • Solo lectura
  • Solo miembros de la rikma

List the categories a product of this rikma can be filed under: the rikma's own (scope "rikma") and the platform-wide ones (scope "platform"), with id, name, slug and parent. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.

getUploadSessionTool

Read an upload link
  • Solo lectura

List the pictures uploaded through an upload link (from createUploadSession): uploadId, url, file name, width and height, in the order they arrived. Pass the uploadIds to setProductImages or createRikmaProduct. Only the user who created the link can read it.

Entradas
token string obligatorio
The token createUploadSession returned.

Preparar

Devuelve un enlace o una propuesta, o guarda un borrador que no obliga a nadie. Las personas aprueban en el sitio.

proposeRikmaBlueprintTool

Draft a rikma from a blueprint
  • Cambia datos
  • Solo miembros de la rikma

Turn a business, an existing partnership or an idea into a draft rikma on 1lev1: the rikma, its PRODUCTS, missions, resources and partners. Use it when someone wants to add their business so the concierge can find and order from them, to see how their partnership would look on 1lev1, or to break an idea down and recruit partners. Build it yourself from the site you read or from the conversation: - products FIRST: every distinct thing they sell is a product, with its price when it is stated (do not invent prices - leave price out and ask), and `keywords`: the words a customer would use for the need it answers, not the product name (a "brunch tray" answers "catering", "breakfast for guests"), and `categories`: 1-3 broad domains ("events", "food") - they are linked to the platform's existing categories, which the concierge compares with every wish. - missions and resources only when they make a product (put their refs in the product recipe) or when someone is still needed. holder "me" = the person you are talking to does it; holder "open" = recruit someone; holder "partner" + partnerRef = an exact `ref` from a row in `partners`. For every partner to invite, add a partner row with a user-provided email and link each mission/resource they will bring with holder "partner" and partnerRef. Do not invent or infer an email; ask the person for it. A partner row without an email cannot receive email, and a partner without linked missions/resources gets only the general rikma join invitation. - a running cost is priced per period, never as a total: rent or a subscription is a resource with kindOf "monthly" (or "yearly") and its price per month; ongoing work every month is a mission with `recurring: true` and `hours` per month. - `why` on each row: one sentence of where it came from ("the site lists it at 180"). Pass projectId to add to a rikma the person is already a member of. The draft is the user's own; a rikma prepared for another person is prepareForSomeoneElse. Show the rows to the person in the conversation, ask about anything you guessed (prices especially), and confirm every partner email before using it - never invent an address. To invite a partner to contribute, add them in partners with a ref, then set holder:"partner" and partnerRef to that exact ref on each mission/resource they will bring; listing a partner alone does not create a work invitation. Fix what they say with setAssistantItems, then give them reviewUrl: on that page they tick what to create and create it with one click. On creation the server sends a partner invitation email when delivery is allowed; registered partners also get mission/resource invitation cards. The result reports delivery and includes a join link to share if no email could be sent. Nothing exists and no invitation is sent until the person creates it there.

Entradas
fields object obligatorio
products object[] opcional
missions object[] opcional
resources object[] opcional
partners object[] opcional
projectId string opcional
An existing rikma of the caller to import into (from findUserProjectsTool).
sourceText string opcional
The site text or conversation summary this was drawn from.

setAssistantItemsTool

Edit a draft list
  • Cambia datos

Change the draft list with small ops - what the person just told you: keep ("that is right"), drop ("not now", reversible with restore), add, rename, setSpec (price, keywords, hours…), link (a product recipe), setField (the rikma name, description…). Refer to rows only by their key. Rows already created on the platform, or a wish row a supplier answered, cannot be changed here - you get reason "created"/"committed"; send the person to the site for those. Pass the version you last saw; conflict:true means it changed meanwhile (maybe on the site) - show the returned list and ask again.

Entradas
sessionId string obligatorio
expectedVersion integer obligatorio
ops object[] obligatorio
instruction string opcional
The person's words, for the shared transcript.
say string opcional
Your one-line summary of the change, for the transcript.

undoAssistantTool

Undo a draft list change
  • Cambia datos

Undo the last change to the draft list (from here or from the site).

Entradas
sessionId string obligatorio
expectedVersion integer obligatorio

shareRikmaPreviewTool

Share a rikma preview link
  • Cambia datos

Make a read-only link that shows how the drafted rikma would look on 1lev1 - its products, missions, resources, who brings what and an example of how shares form - for the person to send to their partners (no account needed to view; nothing is created). Valid 30 days; calling again replaces the old link, and revoke:true ends it.

Entradas
sessionId string obligatorio
revoke boolean opcional

prepareForSomeoneElseTool

Prepare a rikma for someone else
  • Cambia datos

Prepare a rikma on 1lev1 for ANOTHER person - not the user you are talking to - and get two links to pass on to them: (1) `previewUrl` - the rich public rikma page showing products, missions, hours/rates, resources, values and share split (read-only, safe to share anywhere, and live-synced with behind-the-scenes edits), and (2) `manageUrl` - the behind-the-scenes studio where they can edit everything without logging in first (add/remove missions, products, resources and partners, adjust hours +/- and rates, preview the public page, and click to sign up or claim and create the rikma). Use this when a member markets 1lev1 and sets up a new customer's business, or helps another member get started. NEVER use it for the user themselves; for their own business, partnership or idea use proposeRikmaBlueprint. If it is not clear who the rikma is for, ask before calling. Pass that other person's name and email as the user gave them for this, and the intent and blueprint exactly as prepareSignup takes them (include detailed missions with hours & ratePerHour where relevant so they can tweak hours immediately). Direct `signupUrl` (no account yet) or `receiveUrl` (existing account) is also returned. Nothing is created until the recipient creates it, and the caller keeps no access once claimed. Refused when the email is the user's own. Valid 14 days.

Entradas
name string obligatorio
The name the person gave you to sign up with.
email string obligatorio
The email the person gave you to sign up with - the confirmation goes there.
countries string[] opcional
Country names in English, e.g. ["Israel"].
lang "he" | "en" | "ar" | "ru" | "es" opcional
intent "join" | "business" | "partnership" | "idea" | "order" obligatorio
aboutText string opcional
wishText string opcional
blueprint object opcional
forSomeoneElse boolean obligatorio
Confirms the rikma is for another person, not the user you are talking to.

createProjectTool

Prepare a new rikma
  • Solo lectura

Prepare the "create a Partnership" form (a Partnership is also called a rikma, or "רקמה") and return a link that opens it pre-filled. Nothing is created yet: status is "prepared" until the user opens the link and approves the form. Give the user `url` exactly as returned — do not decode, shorten or rebuild it. A public-benefit or nonprofit initiative is a normal Partnership, not a failed business: every Partnership has a public support page (/project/<id>/support) where anyone can donate to it or fund a specific mission, so the public can cover the members' work hours even when nothing is ever sold.

Entradas
name string obligatorio
The name of the new Partnership. Required.
desc string opcional
A short public description (plain text, one or two sentences).
details string opcional
Detailed description as raw HTML, e.g. `<h2>Title</h2><p>Body</p>`. Allowed tags: h1, h2, h3, p, ul, ol, li, strong, em, u, s, a, br, blockquote. Do NOT HTML-escape it (send `<p>`, not `&lt;p&gt;`).
url string opcional
A link to a website related to the project.
vals string[] opcional
Values and goals of the partnership, as their names. A value may contain commas.
res "feh" | "sth" | "nsh" | "sevend" opcional
Response time ID: feh (48h), sth (72h), nsh (96h), sevend (1 week).
profit "already" | "week" | "month" | "threeM" | "sixM" | "oneY" | "twoY" | "more" | "never" opcional
When the Partnership expects to earn from sales: already, week, month, threeM, sixM, oneY, twoY, more, or never. `never` is the correct value for a nonprofit / public-benefit initiative - it means "selling is not the goal", not "it will fail". Such a Partnership is funded through its public support page, where donors can cover the work hours.
ont boolean opcional
Whether the partnership is continuous (true) or a one-time event (false).

prepareMissionTool

Prepare a mission
  • Solo lectura
  • Solo miembros de la rikma

Prepare the mission creation form and return a link that opens it pre-filled. Use this when the user should review and confirm the mission before it is published. A mission is for work that needs an implementer to be found. If a mission in progress already covers the work, create a task (act) on it with createTaskTool instead. Check the rikma's open missions (getProjectDetailsTool) first: when one already covers the work, point the user to it rather than preparing a duplicate. Mission names are also entries in a platform-wide catalogue where each name is unique; publishing a name that is already there reuses that catalogue entry automatically (the rikma's mission keeps its own description, hours and rate), so never rename a mission just to make it unique. Nothing is created yet: status is "prepared" until the user opens the link and publishes. Give the user `url` exactly as returned — do not decode, shorten or rebuild it. Requires a projectId - use findUserProjects first if not known.

Entradas
projectId string obligatorio
ID of the project where the mission will be created.
name string obligatorio
Mission name (required).
descrip string opcional
Mission description as rich HTML - strongly preferred over plain text; a partner decides whether to join from this. Allowed tags: h1, h3, p, ul, ol, li, strong, em, a, br. Recommended shape: a short intro <p>, then a <ul> of concrete deliverables and what done looks like. Do NOT HTML-escape it (send `<p>`, not `&lt;p&gt;`).
skills string[] opcional
Skill names, free text in the user's language. Matched to the platform catalogue; a skill that does not exist yet is created. Up to 8.
roles string[] opcional
Role names, free text. Matched to the catalogue; created when missing. Up to 8.
workways string[] opcional
Work-mode names (how the work is done, e.g. "remote", "on-site"), free text. Matched to the catalogue; created when missing. Up to 8.
nhours number opcional
Estimated hours.
valph number opcional
Value per hour.

planProjectWorkTool

Plan rikma work from an idea
  • Cambia datos
  • Solo miembros de la rikma

Turn a free-text brief into a planning board for a project: proposed missions, chores (acts) and resources, deduplicated against what the project already has. Nothing is created - the tool returns a reviewUrl where the user approves each row in the real form. Use this when the user describes something they want the project to achieve in loose words. If the conversation already holds a concrete breakdown (tasks, scope, decisions), use createPlanBoardTool instead - it saves your rows as written. Requires a projectId (use findUserProjectsTool first if unknown). On failure, `error.retryable` says whether calling again can help.

Entradas
projectId string obligatorio
ID of the project to plan for.
text string obligatorio
What the user wants to advance, in their own words. At least 20 characters - the richer the brief, the better the breakdown.
title string opcional
Optional title for the board; otherwise one is suggested.

createPlanBoardTool

Save a planning board
  • Cambia datos
  • Solo miembros de la rikma

Create a planning board from rows YOU already structured. Use this when the conversation already holds the breakdown - decisions, scope, a task list: your rows are saved as written, with no second model rewriting or dropping them. Nothing is created - every row is a proposal the user approves in the real creation form at the returned reviewUrl. Every row needs a name AND a descrip; rows without one are not saved and come back in `rejected`. Use planProjectWorkTool instead when the user only has a loose idea in free text. Requires a projectId. On failure, `error.retryable` says whether calling again can help.

Entradas
projectId string obligatorio
ID of the project to plan for.
title string obligatorio
Board title - the direction these rows advance.
descrip string opcional
One or two plain-text sentences on what this board is for.
items object[] obligatorio
The rows, in the order the user should see them. 1 to 40.

scanProjectDirectionsTool

Scan rikma directions
  • Cambia datos
  • Solo miembros de la rikma

Cheaply scan a project's real current state and propose a few DIRECTIONS for advancing it - strategic angles, not task lists. Use this when the user asks something open-ended like "what should we do next?" or "how do we move this forward?" and has not described a specific goal. These are saved as suggested directions only: nothing is created, and no mission, chore or resource comes out of this call. To break one direction down into concrete missions and resources afterwards, the user opens it on the returned reviewUrl and approves each row there. Requires a projectId. On failure, `error.retryable` says whether calling again can help.

Entradas
projectId string obligatorio
ID of the project to scan.

Tus registros

Cambia solo tus propios registros - tus temporizadores, tu perfil, tus borradores.

startAssistantTool

Start a profile or wish list
  • Cambia datos

Open the person's living list of (a) their PROFILE - skills, roles, ways of working, values, resources they own - seeded from what is on it now, plus what `text` says about them (pass what they told you); or (b) a WISH - pass ratsonId (from listMyWishesTool), or `text` to start a new draft wish from their words. Returns the rows with keys. Then refine with setAssistantItems (your own ops - preferred) or reviseAssistant (their words), and save with applyAssistant. A rikma is not started here: use proposeRikmaBlueprint.

Entradas
kind "profile" | "wish" obligatorio
text string opcional
ratsonId string opcional

reviseAssistantTool

Revise a list from free text
  • Cambia datos

Change a list with the person's own words ("that's right, drop the second, add photography") - the platform turns them into ops. Prefer setAssistantItems when you can name the ops yourself; this one runs a model.

Entradas
sessionId string obligatorio
expectedVersion integer obligatorio
instruction string obligatorio

applyAssistantTool

Save a list
  • Cambia datos
  • Puede sobrescribir

Save a list: a PROFILE is saved to their profile right away (what they set aside leaves it; resources are only added). A WISH: its own rows are saved - a draft stays a draft (publishing is theirs, on the site: siteUrl), and rows a supplier already answered are never changed here. A RIKMA is never created here - you get the reviewUrl to give them.

Entradas
sessionId string obligatorio
expectedVersion integer obligatorio

dismissOfferTool

Stop suggesting a mission
  • Cambia datos

The person says an open mission suggested to them is not relevant: it stops being suggested to them. A filter for them only - nobody is told no.

Entradas
openMissionId string obligatorio

timerActionTool

Start or stop a mission timer
  • Cambia datos

Perform actions on user timers (start, stop, pause, resume)

Entradas
action "start" | "stop" | "pause" | "resume" obligatorio
The action to perform on the timer
missionId string opcional
Specific mission ID (optional, will find active timer if not provided)

logLeadActivityTool

Log a lead conversation
  • Cambia datos
  • Solo miembros de la rikma

Record a conversation the member had with a lead — a call, a WhatsApp, an email, a meeting, or a note — in the lead's log, as the member. The first outgoing contact with a new lead marks it "contacted". Only log what the member told you happened; never invent a conversation. Members only.

Entradas
projectId string obligatorio
Rikma id.
leadId string obligatorio
Lead id.
kind "note" | "call" | "whatsapp" | "email" | "meeting" obligatorio
note · call · whatsapp · email · meeting
direction "out" | "in" opcional
'out' = the member reached them, 'in' = they reached the member. Not for notes.
body string opcional
What was said or agreed, in the member's words.
at string opcional
When it happened, ISO (default now; up to 30 days back).

createRikmaProductTool

Create a rikma product
  • Cambia datos
  • Solo miembros de la rikma

Create a fixed-price product (Matanot) for the rikma. Three hosting modes (PLAN_USER_OFFERINGS §3.3): `projectId` alone → the product lives on that rikma (caller must be a member); without it → personal offer hosted on the caller’s home rikma (origin=personal); `newRikmaName` → a fresh named rikma is created first and hosts it. Use it for the storefront: name, description, price, stock (quant, -1 = unlimited), kindOf (total/monthly/yearly/daily/unlimited), location, an uploaded cover (picId) and — on a rikma — galleryIds, categories, options and variants in the same call. For a complex recipe (BOM, margin, estimated price) use createComplexMatanot in the UI — the MCP creates the simple, shippable shelf item. Members or personal owner. Returns the new Matanot id and where it lives.

Entradas
name string obligatorio
Product name — shown in the catalog and on the /gift page.
descrip string opcional
Long description shown to the buyer.
price number obligatorio
Fixed price in the rikma currency (or the currency code you pass).
quant number opcional
Available quantity: a number, -1 for unlimited, or omit for 0.
kindOf "total" | "monthly" | "yearly" | "daily" | "unlimited" opcional
How price×quantity is understood. Default total.
pricingMode "fixed" | "estimated" | "quote" opcional
fixed = sold at this price (checkout:true, what the storefront reports), estimated = shown as estimate, quote = price on request. Default fixed.
projectId string opcional
Host it on this rikma (you must be a member). Omit for a personal offer on your home rikma.
newRikmaName string opcional
Create a fresh rikma with this name and host the product there. Not combined with projectId.
picId string opcional
Strapi upload id of the cover image.
location object opcional
Where the product is (or isOnline:true via location_mode online).
galleryIds string[] opcional
With projectId: more upload ids after the cover, in order.
categories string[] opcional
With projectId: category ids from listRikmaCategories.
options object[] opcional
With projectId: option axes (size, colour…) to make sure exist before the variants.
variants object[] opcional
With projectId: variants, each { optionValues: { size: "M" }, sku?, price?, quant?, active?, position?, imageIds? } — see upsertProductVariants.

updateRikmaProductTool

Update rikma product
  • Cambia datos
  • Solo miembros de la rikma

Update shop-facing fields of a product: hideFromDiscovery (show/hide in the public /gift directory), and `kindOf` for operational edits. More broadly this is the merchant-facing "show/hide" for discovery — what the sales/manage products tab does. Pricing of a rikma product is a term and belongs in editObject with rikma consent (§4.6); this tool says so and returns the edit URL when asked to change price on such a product. For discovery, the change applies at once.

Entradas
projectId string obligatorio
Rikma id (membership check).
productId string obligatorio
Matanot id (from listRikmaProducts).
hideFromDiscovery boolean opcional
Hide it from /gift directory (true) or show it again (false).
name string opcional
New display name (for personal products this applies at once; for rikma products it is a term).
descrip string opcional
New description.

archiveRikmaProductTool

Archive a rikma product
  • Cambia datos
  • Puede sobrescribir
  • Solo miembros de la rikma

Archive (soft-delete) a personal product (origin=personal) you own. Removing a product that belongs to the rikma is a consent flow (proposeObjectArchive — members approve, silence approves at restime), so for those this tool returns the moach link instead of archiving. An archived product stays reachable at /gift/[id] for old orders and sales but vanishes from /gift and the storefront catalog. Never a hard delete — history matters. Unarchiving is done in the moach.

Entradas
projectId string obligatorio
Rikma id the product is listed in.
productId string obligatorio
Matanot id.
archived boolean obligatorio
true = archive. false (unarchive) is not done here — the tool returns the moach link.

setShopStockTool

Set shop stock
  • Cambia datos
  • Solo miembros de la rikma

Update the shelf stock of a product or of one of its variants. Operational change (§4.6): any rikma member may do it, it applies at once, and prices are never touched. Two modes: `set` counts the shelf ("there are 7"), `add` adds a delivery ("12 came in"), reading the quantity on the server first so a sale that landed meanwhile is not overwritten. Use quant=-1 for unlimited. A product that is sold by variant keeps its stock on the variants (Matanot.quant is not used). Members only.

Entradas
projectId string obligatorio
Rikma id.
productId string obligatorio
Matanot id (from listRikmaProducts).
variantId string opcional
Variant id (from listRikmaProductVariants or listRikmaProducts). Required when the product has variants. Pass null/omit for a simple product.
mode "set" | "add" opcional
`set` counts, `add` delivers. Default set.
value number opcional
Units: the new count (`set`) or how many came in (`add`). Ignored when unlimited=true.
unlimited boolean opcional
Pass true for unlimited stock (-1).

updateRikmaOrderStatusTool

Update order status
  • Cambia datos
  • Solo miembros de la rikma

Advance a paid store order to shipped, fulfilled, or cancel it as its holder. Any member may mark shipped/fulfilled (getting the parcel out is the rikma’s work); cancel is holder-only — the member whose till took the money — because it resets their own self-reported sales not yet in a split; sales already in a split are left and the rikma is told to settle the refund. Idempotent (same status twice succeeds quietly); backwards transitions refuse (§3.4). On cancel, pass restock:true to put the items back on the shelf (default: only when the order was not yet shipped). Members only.

Entradas
projectId string obligatorio
Rikma id.
orderRef string obligatorio
Order ref (`<rikma>:<externalId>` as POST /orders answered) or orderId.
action "shipped" | "fulfilled" | "cancel" obligatorio
shipped → parcel left, fulfilled → delivered/picked up, cancel → refund.
reason string opcional
Cancel reason shown on the order and in sale notes.
restock boolean opcional
On cancel: put items back in stock. Default: only when not yet shipped.
trackingNumber string opcional
On shipped: the carrier’s tracking number. The buyer is mailed that it left, with this number.
trackingCarrier string opcional
On shipped: the carrier, e.g. DHL.
trackingUrl string opcional
On shipped: a tracking page (http/https).

proposeProductEditTool

Propose a product edit
  • Cambia datos
  • Solo miembros de la rikma

Change a product's name, description, price, pricing mode or categories. On a rikma product the terms (name, description, price) become an edit proposal to the partners (editObject): the result has proposalId, silenceApprovesAt (when silence approves it at the rikma's restime) and voteUrl — you never approve it. On a personal product, or in a rikma of one, everything applies at once. Categories always apply at once. One open proposal per product: if one is already open, answer it first. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string obligatorio
Matanot id, from listRikmaProducts.
name string opcional
New name. A term.
descrip string opcional
New description. A term.
price number opcional
New base price. A term.
pricingMode "fixed" | "estimated" | "quote" opcional
Personal products only: a rikma product's pricing mode changes its recipe and is changed in the moach.
categories string[] opcional
Replace the categories (ids from listRikmaCategories). Operational — applied at once.
reason string opcional
Why — shown to the partners on the proposal.

proposeProductEditsBatchTool

Propose product edits (batch)
  • Cambia datos
  • Solo miembros de la rikma

proposeProductEdit for up to 50 products of one rikma in one call. A proposal belongs to one product (that is how editObject works: one decision per object, with its own clock and vote), so each product gets its own proposal — or applies at once when it is personal. Every item is answered on its own (results[i]); one failing item never stops the others. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
items object[] obligatorio

setProductImagesTool

Set product pictures
  • Cambia datos
  • Solo miembros de la rikma

Set a product's pictures: the cover (coverId), the gallery after it (galleryIds, in order; max 12 pictures with the cover) and, optionally, each variant's own pictures. Pictures are operational — like stock, they apply at once on every product, rikma or personal, with no proposal: they show the same product, they do not change what anyone agreed to. Ids come from getUploadSession, uploadMediaFromUrl or getRikmaProduct. Omit galleryIds to keep the gallery and only change the cover. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string obligatorio
Matanot id, from listRikmaProducts.
coverId string opcional
Upload id of the cover picture.
galleryIds string[] opcional
Upload ids after the cover, in order. [] clears the gallery but the cover.
variants object[] opcional
Per-variant pictures.

upsertProductOptionsTool

Create or extend product options
  • Cambia datos
  • Solo miembros de la rikma

Create or extend the rikma's option axes — e.g. Size (S, M, L) and Colour (Red #d22, Blue #22d). Axes belong to the rikma and are shared by its products; an axis with the same key gains the new values and keeps the old ones (another product may sell them), labels and swatch colours are updated. Operational: applied at once. Up to 3 axes per call and 30 values per axis. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
options object[] obligatorio

upsertProductVariantsTool

Create or update product variants
  • Cambia datos
  • Solo miembros de la rikma

Create or update variants of a product. Each item names its options ({ "size": "M", "color": "Red" } — the axes must exist: upsertProductOptions), and the axisKey is built from them. An item with variantId, or with options that match an existing variant, updates it; otherwise a new variant is created. Only the fields you pass move. Stock (quant, -1 unlimited), active, SKU, position and pictures apply at once. On a rikma product a new variant, or a price that moves, goes to the partners as one edit proposal (proposalId, silenceApprovesAt, voteUrl); on a personal product everything applies at once. Variants are never deleted — set active:false. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string obligatorio
Matanot id, from listRikmaProducts.
variants object[] obligatorio
reason string opcional
Why — shown to the partners when something is proposed.

setProductCategoriesTool

Set product categories
  • Cambia datos
  • Solo miembros de la rikma

Replace the categories of a product with these ids (from listRikmaCategories; [] removes them all). Where a product is filed is operational — applied at once, no proposal. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string obligatorio
Matanot id, from listRikmaProducts.
categoryIds string[] obligatorio

createRikmaProductsBatchTool

Create products (batch)
  • Cambia datos
  • Solo miembros de la rikma

Create up to 30 products in one rikma in one call — each with the same fields as createRikmaProduct: name, description, price, stock, pictures (picId + galleryIds), categories, options and variants. Every item is created and answered on its own (results[i] with productId, or why it failed); one failure never stops the rest. A product whose extras failed is still created and marked partial. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
items object[] obligatorio

createUploadSessionTool

Create a picture upload link
  • Cambia datos
  • Solo miembros de la rikma

Get a short-lived link where the user uploads product pictures from their phone or computer — use it when the user has pictures you cannot read (you do not get the bytes of attachments). Give the user the url; when they say they are done, call getUploadSession with the token to get the upload ids, then setProductImages. JPG/PNG/WebP only, up to maxFiles pictures (default 10, max 20), valid for 60 minutes. The link only adds pictures to the media library — it attaches nothing and shows no rikma data. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string opcional
The product the pictures are for (shown on the page; attaching is still setProductImages).
maxFiles integer opcional
How many pictures the link accepts. Default 10.

uploadMediaFromUrlTool

Upload a picture from a URL
  • Cambia datos
  • Solo miembros de la rikma

Upload one product picture from a public URL (the server downloads it) or from base64 (for agents that can read files; up to 3MB). The bytes must really be JPG, PNG or WebP (checked, not trusted from the name); a URL picture is up to 10MB. Internal or private addresses are refused. Returns uploadId for setProductImages or createRikmaProduct. For pictures the user attached to the chat, use createUploadSession instead. Members only.

Entradas
projectId string obligatorio
Rikma (project) id, from findUserProjectsTool. You must be a member.
url string opcional
Public http(s) URL of the picture.
base64 string opcional
The picture as base64 or a data: URL. Use url or base64, not both.
fileName string opcional
A name for the stored file.

Espera consentimiento

Deja algo a otro miembro, y queda esperando su aprobación.

proposeProjectLinkTool

Propose a rikma link
  • Cambia datos
  • Solo miembros de la rikma

Set or clear one of a rikma's links - its website, GitHub repo, Drive, Discord, Facebook, X or WhatsApp. In a rikma with more than one member, changing the website or the Facebook link opens a decision the members vote on (silence approves it when the rikma clock runs out); the other links change directly. Members only. Check listProjectResourcesTool first - the link may already be there.

Entradas
projectId string obligatorio
Rikma (project) id.
kind "website" | "github" | "drive" | "discord" | "facebook" | "x" | "whatsapp" obligatorio
Which link to set.
url string obligatorio
The URL. Pass an empty string to clear the link.

createTaskTool

Propose a task
  • Cambia datos
  • Solo miembros de la rikma

Create a task (Act, "מטלה") in a project - the way a member gets something new done. Whenever the user wants something new to happen in a project, offer this option. Choose the shape: - A mission in progress already covers the work: create an act linked to it - assignedUserId = the mission holder, missionId from getMemberMissionsTool. - Nobody in the project does this kind of work, so an implementer must be found: this is not an act - prepare a mission with prepareMissionTool. - No specific person yet: create the act with no assignee and pass tafkidims = the roles that fit it (IDs from getProjectMembersTool). The holders of those roles are notified and one of them picks it up. An act assigned to another person waits for that person to approve it; nobody is bound until they accept. The caller must be a member of the project. Requires a project ID.

Entradas
projectId string obligatorio
ID of the project where the task will be created
name string obligatorio
Short name/title of the task
description string opcional
What has to be done and what done looks like, as plain text. Strongly recommended - a title alone is hard to act on.
link string opcional
Optional URL related to the task
assignedUserId string opcional
ID of the person (project member) to assign this task to - usually the holder of the mission it belongs to. Use getProjectMembersTool to resolve a name to an ID. Mutually exclusive with tafkidims.
tafkidims string[] opcional
IDs of the roles (tafkidim) that fit the task, when no specific person is chosen; a holder of one of them picks it up. Use getProjectMembersTool to resolve role names to IDs. Mutually exclusive with assignedUserId.
missionId string opcional
ID of the mission in progress (mesimabetahaliches) this task belongs to, from getMemberMissionsTool. Goes with assignedUserId.
hashivut "white" | "green" | "yellow" | "red" opcional
Urgency level of the task
dateS string opcional
Start date (ISO format)
dateF string opcional
End date (ISO format)

applyToMissionTool

Apply to an open mission
  • Cambia datos

Send the user's own candidacy for an open mission, on the mission's stated terms (hours, hourly rate). It binds nobody: the rikma's members sign it, discuss it or counter it, and silence approves it when the rikma's clock runs out. BEFORE calling, read the mission name, hours and rate back to the user and get their yes - then pass confirmedWithUser: true. When the mission is part of a customer's deal, every customer of that deal must sign too: the first call returns needsCustomerSignature and applies nothing; tell the user, and call again with customerSignatureUnderstood: true only if they still want to. To propose different terms, give the user the mission page instead. Ids come from listMyMatchesTool or searchCatalogTool.

Entradas
openMissionId string obligatorio
The open mission id.
confirmedWithUser boolean obligatorio
true only after the user heard the mission name, hours and rate and said yes.
customerSignatureUnderstood boolean opcional
true only after the user was told the deal's customers must also sign, and still wants to apply.

Comunicar

Visible para otros en tu nombre, y no obliga a nadie.

postConversationMessageTool

Post to a conversation
  • Cambia datos

Post a message, as the user, in a conversation (forum) they take part in - an update on a mission, an answer in a decision thread, a note on a profit split. The other participants are notified. Use it ONLY when the user asked to say or record something; never to think out loud, and never to agree or refuse on their behalf (approving a decision, a split or a proposal is always their own click). The message is marked as written through an agent.

Entradas
forumId string obligatorio
Forum id, from listMyConversations.
message string obligatorio
The message, in the user's own words and language. Plain text.

openRikmaConversationTool

Open the rikma conversation
  • Cambia datos
  • Solo miembros de la rikma

Get the rikma's own general conversation - the one thread that belongs to the whole rikma rather than to a single mission, act or decision. It is created the first time someone opens it. Use it for "what are we doing next" talk; anything about a specific mission, decision or profit split belongs in that thing's own thread, where it stays on record. Returns a forumId for readConversation and postConversationMessage. Members only.

Entradas
projectId string obligatorio
Rikma (project) id.

startProcessTool

Start a process
  • Cambia datos
  • Solo miembros de la rikma

Start a process in a rikma: a named thread with its own conversation, for something that is not yet a mission or a resource - approaching an organisation, preparing a launch, chasing funding. The description becomes the first message, so a half-formed idea can be written in plain words and take shape later: as it becomes concrete, the open missions and resources it needs are created in the normal way and attached with attachToProcess. Members only. Use it when the user wants to record something the rikma is pursuing, not to file your own notes.

Entradas
projectId string obligatorio
Rikma (project) id.
name string obligatorio
Short name, e.g. "Approach: city community centre".
description string opcional
The raw text, in the user's own words: what this is, who it involves, what is hoped for.

attachToProcessTool

Attach to a process
  • Cambia datos
  • Solo miembros de la rikma

Attach an existing object - an open mission, an open resource, a mission in progress, or a mission/resource still being voted on - to a process, so what the rikma is pursuing and what it is actually doing about it stay connected. It does not create the object: create it first (prepareMissionTool, createTaskTool, or the URL the tool returns), then attach it.

Entradas
projectId string obligatorio
Rikma (project) id.
processId string obligatorio
Process id, from listRikmaProcesses or startProcess.
entityType "openMission" | "openMashaabim" | "mesimabetahalich" | "maap" | "pendm" | "pmash" obligatorio
What kind of object is being attached.
entityId string obligatorio
Id of that object.
name string opcional
Its name, for the process timeline.

Escritura compartida

Crea obligaciones para otras personas. Desactivado salvo que la clave tenga el permiso mcp:write.

createMissionTool

Create an open mission
  • Cambia datos
  • Solo miembros de la rikma
  • Necesita el permiso mcp:write

Create a new mission directly in a project. Resolves skill/role/workway names to platform IDs via vector search (Pinecone), creating new vocabulary entries when needed. Use prepareMissionTool instead when you want the user to review the mission before publishing.

Entradas
projectId string obligatorio
ID of the project where the mission will be created.
missionName string obligatorio
Name of the mission (required).
descrip string opcional
Mission description (plain text or HTML).
skills string[] opcional
Skill names needed for the mission.
roles string[] opcional
Role/position names for the mission.
workways string[] opcional
Work mode names (remote, onsite, hybrid…).
nhours number opcional
Estimated hours.
valph number opcional
Value per hour (₪/$ per hour).
iskvua boolean opcional
True if this is a recurring monthly mission.
dateStart string opcional
Start date (ISO 8601).
dateEnd string opcional
End date (ISO 8601).
assignedUserId string opcional
User ID to assign the mission to (omit for open/voted).
checklist object[] opcional
Optional checklist tasks for the mission.

Privacidad

Nuevo deseo