تخطٍ إلى المحتوى الرئيسي

ربط وكيل ذكاء اصطناعي بحسابك

الوكيل الذي تعملون معه أصلاً يستطيع إدارة شراكاتكم دون فتح المتصفح.

أمر واحد، وينتهي الأمر

يفتح الأمر موقع 1lev1 في المتصفح، فتوافقون على الربط، ويُكتب المفتاح تلقائياً في كل وكيل مثبت لديكم — مع المهارة.

npx 1lev1-mcp

أعيدوا تشغيل الوكيل بعد ذلك كي يقرأ الإعدادات الجديدة.

من الهاتف والمتصفّح — بدون طرفية

يتّصل تطبيق Claude، وموقع claude.ai، ومحرّر Claude Code في المتصفّح عبر connector: تلصق عنواناً واحداً، توافق في المتصفّح، وانتهى الأمر. لا مفتاح تنسخه ولا ملف إعدادات تحرّره.

أضِف إلى Claude بنقرة واحدة
  1. اضغط الزرّ. يُفتح claude.ai على نافذة الإضافة، والاسم والعنوان معبّآن مسبقاً.
  2. اضغط Add ثم Connect. تُفتح صفحة 1lev1، سجّل الدخول ووافق على الاتصال.
  3. انتهى. اتصال واحد يكفي للمحادثة على الحاسوب وللتطبيق على الهاتف ولـ Claude Code في المتصفّح معاً.

لم يُفتح الزرّ؟ افتح الإعدادات ← Connectors ← Add custom connector، أعطِه اسماً — 1lev1 مثلاً — والصق عنوان الخادم أدناه.

عنوان الخادم

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

ينشئ الاتصال مفتاح API عادياً في حسابك. يظهر في صفحة مفاتيح API ويُلغى من هناك، تماماً كمفتاح أُنشئ من الطرفية.

Claude Code — عبر الإضافة

من يعمل في Claude Code يستطيع تثبيت المهارة من السوق، ثم ربط الحساب بالأمر أعلاه.

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

الإضافة تجلب المعرفة، وأمر الربط يجلب الوصول. كلاهما مطلوب.

ماذا يمكنكم أن تطلبوا

  • على ماذا يفترض أن أعمل اليوم؟
  • ابدأ المؤقت على مهمة الشعار.
  • عملت أمس ثلاث ساعات على التصميم — سجّلها.
  • كم ساعة تراكمت لي في هذه الشراكة؟
  • حوّل هذا المستودع إلى شراكة بيننا نحن الثلاثة.
  • ما الذي ينتظر موافقتي؟

ما الذي لن يفعله الوكيل نيابة عنكم

1lev1 قائمة على الموافقة، لذلك لا ينفّذ الوكيل أي فعل يمسّ شخصاً آخر. بل يحضّر النموذج ويرسلكم للموافقة عليه في الموقع.

  • لا يصوّت ولا يوقّع على تقسيم أرباح مكانكم.
  • لا يقبل العروض ولا يغيّر وضع عضو آخر في الشراكة.
  • لا يرى بيانات أي مستخدم آخر — المفتاح مرتبط بحسابكم وحده.
  • إنشاء المهام والمهمات للآخرين معطّل افتراضياً ويحتاج إذناً صريحاً.

ما هذا بالضبط

MCP بروتوكول مفتوح يتيح لوكيل الذكاء الاصطناعي الاتصال بخدمات خارجية. خادم MCP الخاص بـ 1lev1 يمنح وكيلكم الوصول إلى مهامكم ومؤقتاتكم وشراكاتكم — وإليها وحدها. أما المهارة المثبتة إلى جانبه فتعلّم الوكيل كيف تعمل المنصة: ما هي الشراكة، ولماذا الساعات المسجلة هي ملكية، وما الذي لا يجوز له فعله نيابة عن شخص آخر.

الوكلاء المدعومون

يكتشف الأمر ما هو مثبت لديكم فعلاً ويكتب إليه وحده: Claude Code، Claude Desktop، Cursor، Windsurf، Cline، Roo Code، Continue، Antigravity، VS Code. ولا يمسّ أي ملف إعدادات يعجز عن قراءته، ويحفظ نسخة احتياطية قبل كل تغيير.

ChatGPT، Gemini، ووكلاء آخرون

يتحدّث الخادم بروتوكول MCP القياسي، لذا فهو ليس حكراً على Claude. ما يعمل اليوم:

  • ChatGPT — فعّل Developer mode في الإعدادات، وأضف connector بعنوان الخادم نفسه، ثم وافق في المتصفّح. متاح في الاشتراكات المدفوعة.
  • Gemini CLI، Antigravity — أمر الاتصال أعلاه يكتب إليهما مباشرة، كأي محرّر آخر.
  • Gemini Enterprise — يضيف مدير المؤسسة خادم MCP مخصّصاً ضمن Connected apps. يتطلّب ذلك معرّف عميل وسرّاً يدويّين — راسِلنا ونصدرهما لعنوان الإرجاع الخاص بمؤسستك.
  • Codex CLI — يُضاف يدوياً إلى الملف ‎~/.codex/config.toml، مع بقاء المفتاح في متغيّر بيئة لا في الملف نفسه.
  • n8n أو Zapier أو وكيل كتبته بنفسك — أي عميل MCP يدعم Streamable HTTP مع ترويسة Authorization سيعمل مع العنوان نفسه.
[mcp_servers.lev1]
url = "https://api.1lev1.com/api/mcp"
bearer_token_env_var = "LEV1_API_KEY"

تطبيق Gemini للمستخدمين لا يتيح بعد إضافة خادم MCP بنفسك — الاتصالات هناك تُفتح عبر شراكات مع Google فقط.

إعداد يدوي

إذا لم يكن وكيلكم في القائمة، يمكنكم إضافة الخادم يدوياً. احصلوا على المفتاح من الأمر أعلاه.

عنوان الخادم

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

الأمان وفكّ الارتباط

  • المفتاح كلمة سر بكل معنى الكلمة. لا تشاركوه ولا تضعوه في شيفرة محفوظة في git.
  • الموافقة مجدداً من الموقع تستبدل المفتاح السابق وتلغي الوصول القديم.

لفكّ الارتباط تماماً، يزيل هذا الأمر الخادم والمهارة من كل الوكلاء.

npx 1lev1-mcp remove

هذا الأمر ينظّف الإعدادات على جهازكم فقط — أما المفتاح نفسه فيبقى صالحاً. لإبطاله، شغّلوا أمر الربط من جديد ووافقوا: فهو يستبدل المفتاح السابق.

لمساعدي الذكاء الاصطناعي

دليل الأدوات

كل الأدوات التي يمنحها الموصل لحساب مسجّل الدخول، كما يعيدها الخادم نفسه - فهذه القائمة هي دائمًا ما يحصل عليه مساعدك. أوصاف الأدوات هي ما يقرؤه المساعد، لذا تبقى بالإنجليزية.

كيف يتعامل الموصل مع معلوماتك

بلا حساب

تعمل قبل أن يسجّل أي شخص الدخول. ‏prepareSignup يحفظ مسودة تسجيل لمن ليس لديه حساب بعد - اسمه وبريده وما جاء من أجله - لا تُلزم أحدًا حتى يوقّعها بنفسه، وتنتهي صلاحيتها بعد 14 يومًا. كل أداة أخرى تطلب تسجيل الدخول أولًا.

getPlatformInfo

About 1lev1
  • قراءة فقط

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

المدخلات

لا مدخلات.

prepareSignup

Prepare a signup
  • يغيّر البيانات

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.

المدخلات
name string إلزامي
The name the person gave you to sign up with.
email string إلزامي
The email the person gave you to sign up with - the confirmation goes there.
countries string[] اختياري
Country names in English, e.g. ["Israel"].
lang "he" | "en" | "ar" | "ru" | "es" اختياري
intent "join" | "business" | "partnership" | "idea" | "order" إلزامي
aboutText string اختياري
wishText string اختياري
blueprint object اختياري

قراءة

قراءة فقط. تعيد ما كنت ستراه بنفسك على الموقع.

findUserProjectsTool

Find my rikmas
  • قراءة فقط

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.

المدخلات
userId string اختياري
User id to list projects for. Omit to use the authenticated caller.
query string اختياري
Optional search query to filter projects by name (case-insensitive substring).
limit integer اختياري
Page size, default 50.
offset integer اختياري
How many results to skip, default 0.

getProjectDetailsTool

Get rikma details
  • قراءة فقط

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).

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.

listProjectResourcesTool

List rikma resources
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.

getProjectStatsTool

Get rikma stats
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.
days integer اختياري
Window for the "recent" numbers, default 30.

getProjectMembersTool

List rikma members
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project
query string اختياري
Optional text to filter people or roles by name

getMemberMissionsTool

List a member's missions
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project
userId string إلزامي
ID of the member (assignee) whose in-progress missions to list

getMissionDetailsTool

Get mission details
  • قراءة فقط
  • لأعضاء الريكما فقط

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

المدخلات
missionId string إلزامي
Mission ID to get details for

listUserMissionsTool

List my missions
  • قراءة فقط

List user missions with various filtering options

المدخلات
filter "all" | "active" | "completed" | "startable" | "stoppable" | "overdue" اختياري
Filter missions by status
projectId string اختياري
Filter by specific project ID (numeric)
projectName string اختياري
Filter by project name
missionName string اختياري
Search for missions by name (partial match)
limit number اختياري
Maximum number of missions to return

findMissionTool

Find one of my missions
  • قراءة فقط

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.

المدخلات
missionName string إلزامي
The name of the mission to find.

getActiveTimersTool

Get running timers
  • قراءة فقط

Get all currently active timers for the user

المدخلات
includeDetails boolean اختياري
Include detailed timer information

getMissionStatsTool

Get mission stats
  • قراءة فقط

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

المدخلات
projectId string اختياري
Get stats for specific project only

searchCatalogTool

Search the catalog
  • قراءة فقط

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.

المدخلات
query string إلزامي
Free text; matched against names, descriptions and rikma names.
kinds "products" | "missions" | "resources"[] اختياري
Which directories to search. Default: all three.
limit integer اختياري
Maximum rows per kind, default 10.

searchRikmasTool

Search rikmas
  • قراءة فقط

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.

المدخلات
query string اختياري
Free text. Empty: the newest rikmas.
limit integer اختياري
Maximum rows, default 10.

listMyMatchesTool

List my matches
  • قراءة فقط

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.

المدخلات
limit integer اختياري
Maximum rows, default 10.

getMyStakeTool

Get my share in a 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.

المدخلات
projectId string إلزامي
The rikma id (findUserProjectsTool).

listMyApplicationsTool

List my applications
  • قراءة فقط

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`.

المدخلات

لا مدخلات.

getDecisionTool

Get a decision
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
The rikma id.
decisionId string إلزامي
The decision id.

getRikmaLedgerTool

Get rikma sales and splits
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
The rikma id (findUserProjectsTool).

findPartnersTool

Find partners by skill
  • قراءة فقط

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.

المدخلات
query string إلزامي
A skill or role, a word or two.
limit integer اختياري
Maximum named people, default 10.

searchContentTool

Search my rikmas
  • قراءة فقط

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.

المدخلات
query string إلزامي
Free text; matched against names and descriptions.
limit integer اختياري
Maximum rows per kind, default 10.

listMyWishesTool

List my wishes
  • قراءة فقط

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.

المدخلات

لا مدخلات.

getWishDetailsTool

Get wish details
  • قراءة فقط

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.

المدخلات
wishId string إلزامي
Wish (ratson) id, from listMyWishes or a /concierge or /wish URL.

listMyWishOffersTool

List offers on my wishes
  • قراءة فقط

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.

المدخلات

لا مدخلات.

getMyUpdatesTool

What's waiting for me
  • قراءة فقط

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.

المدخلات
projectId string اختياري
Only this rikma (its id, e.g. from findUserProjectsTool).
rikma string اختياري
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" اختياري
The language to word the sentences in. Default: the user's language.
limit integer اختياري
How many waiting items at most (default 20).

getAssistantTool

Get a draft list
  • قراءة فقط

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.

المدخلات
kind "rikma" | "profile" | "wish" اختياري
Latest session of this kind.
sessionId string اختياري

listMyConversationsTool

List my conversations
  • قراءة فقط

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.

المدخلات
projectId string اختياري
Only conversations of this rikma.
limit integer اختياري
Maximum rows, default 25.

readConversationTool

Read a conversation
  • قراءة فقط

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.

المدخلات
forumId string إلزامي
Forum id, from listMyConversations.
limit integer اختياري
How many of the most recent messages, default 30.

getSitePagesTool

List site pages
  • قراءة فقط

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

المدخلات

لا مدخلات.

listRikmaProcessesTool

List rikma processes
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.

listRikmaProductsTool

List rikma products
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.
includeArchived boolean اختياري
Also return archived products. Default false.
kindOf string اختياري
Filter by kindOf: total, monthly, yearly, daily, unlimited.
search string اختياري
Free-text filter over name (case-insensitive, in-memory).

getRikmaProductTool

Get rikma product
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.
productId string إلزامي
Matanot id (from listRikmaProducts).
includeArchived boolean اختياري
Allow a row that is archived lifecycle=false. Default true for a direct get.

getShopInventoryTool

Get shop inventory
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.
includeArchived boolean اختياري
Count archived products in the totals. Default false.

listRikmaProductOptionsTool

List product options
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.

listRikmaProductVariantsTool

List product variants
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.
productIds string[] إلزامي
Matanot ids to pull variants for (from listRikmaProducts).

listRikmaOrdersTool

List rikma orders
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.
status "paid" | "shipped" | "fulfilled" | "cancelled" اختياري
Filter to one lifecycle state.
oversoldOnly boolean اختياري
Only orders whose stock ran short.
limit integer اختياري
Return at most this many, default 50.

getRikmaOrderTool

Get rikma order
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.
orderRef string إلزامي
The order ref, e.g. "57:pi_3Q8x…" — or an orderId (the tool tries both).

listRikmaLeadsTool

List rikma leads
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id, from findUserProjectsTool.
view "open" | "attention" | "paused" | "mine" | "nobody" اختياري
'open' (default): everything in play · 'attention': needs someone now · 'paused': not now · 'mine' · 'nobody': nobody took it
limit integer اختياري
At most this many rows, default 30.

getLeadTool

Get a lead
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id.
leadId string إلزامي
Lead id, from listRikmaLeadsTool (rows of kind "lead").
logLimit integer اختياري
How many log entries, default 20.

getShippingConfigTool

Get shipping setup
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.

quoteShippingTool

Quote shipping
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool.
items object[] إلزامي
What is being sent.
address object اختياري
Where it goes. Omit to see pickup/digital options and which methods would need an address.

listRikmaCategoriesTool

List product categories
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.

getUploadSessionTool

Read an upload link
  • قراءة فقط

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.

المدخلات
token string إلزامي
The token createUploadSession returned.

تحضير

تعيد رابطًا أو اقتراحًا، أو تحفظ مسودة لا تُلزم أحدًا. الناس يوافقون على الموقع.

proposeRikmaBlueprintTool

Draft a rikma from a blueprint
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
fields object إلزامي
products object[] اختياري
missions object[] اختياري
resources object[] اختياري
partners object[] اختياري
projectId string اختياري
An existing rikma of the caller to import into (from findUserProjectsTool).
sourceText string اختياري
The site text or conversation summary this was drawn from.

setAssistantItemsTool

Edit a draft list
  • يغيّر البيانات

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.

المدخلات
sessionId string إلزامي
expectedVersion integer إلزامي
ops object[] إلزامي
instruction string اختياري
The person's words, for the shared transcript.
say string اختياري
Your one-line summary of the change, for the transcript.

undoAssistantTool

Undo a draft list change
  • يغيّر البيانات

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

المدخلات
sessionId string إلزامي
expectedVersion integer إلزامي

shareRikmaPreviewTool

Share a rikma preview link
  • يغيّر البيانات

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.

المدخلات
sessionId string إلزامي
revoke boolean اختياري

prepareForSomeoneElseTool

Prepare a rikma for someone else
  • يغيّر البيانات

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.

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

createProjectTool

Prepare a new rikma
  • قراءة فقط

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.

المدخلات
name string إلزامي
The name of the new Partnership. Required.
desc string اختياري
A short public description (plain text, one or two sentences).
details string اختياري
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 اختياري
A link to a website related to the project.
vals string[] اختياري
Values and goals of the partnership, as their names. A value may contain commas.
res "feh" | "sth" | "nsh" | "sevend" اختياري
Response time ID: feh (48h), sth (72h), nsh (96h), sevend (1 week).
profit "already" | "week" | "month" | "threeM" | "sixM" | "oneY" | "twoY" | "more" | "never" اختياري
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 اختياري
Whether the partnership is continuous (true) or a one-time event (false).

prepareMissionTool

Prepare a mission
  • قراءة فقط
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project where the mission will be created.
name string إلزامي
Mission name (required).
descrip string اختياري
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[] اختياري
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[] اختياري
Role names, free text. Matched to the catalogue; created when missing. Up to 8.
workways string[] اختياري
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 اختياري
Estimated hours.
valph number اختياري
Value per hour.

planProjectWorkTool

Plan rikma work from an idea
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project to plan for.
text string إلزامي
What the user wants to advance, in their own words. At least 20 characters - the richer the brief, the better the breakdown.
title string اختياري
Optional title for the board; otherwise one is suggested.

createPlanBoardTool

Save a planning board
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project to plan for.
title string إلزامي
Board title - the direction these rows advance.
descrip string اختياري
One or two plain-text sentences on what this board is for.
items object[] إلزامي
The rows, in the order the user should see them. 1 to 40.

scanProjectDirectionsTool

Scan rikma directions
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project to scan.

سجلاتك

تغيّر سجلاتك أنت فقط - مؤقّتاتك وملفك ومسوداتك.

startAssistantTool

Start a profile or wish list
  • يغيّر البيانات

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.

المدخلات
kind "profile" | "wish" إلزامي
text string اختياري
ratsonId string اختياري

reviseAssistantTool

Revise a list from free text
  • يغيّر البيانات

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.

المدخلات
sessionId string إلزامي
expectedVersion integer إلزامي
instruction string إلزامي

applyAssistantTool

Save a list
  • يغيّر البيانات
  • قد يستبدل

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.

المدخلات
sessionId string إلزامي
expectedVersion integer إلزامي

dismissOfferTool

Stop suggesting a mission
  • يغيّر البيانات

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.

المدخلات
openMissionId string إلزامي

timerActionTool

Start or stop a mission timer
  • يغيّر البيانات

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

المدخلات
action "start" | "stop" | "pause" | "resume" إلزامي
The action to perform on the timer
missionId string اختياري
Specific mission ID (optional, will find active timer if not provided)

logLeadActivityTool

Log a lead conversation
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

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

createRikmaProductTool

Create a rikma product
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

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

updateRikmaProductTool

Update rikma product
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id (membership check).
productId string إلزامي
Matanot id (from listRikmaProducts).
hideFromDiscovery boolean اختياري
Hide it from /gift directory (true) or show it again (false).
name string اختياري
New display name (for personal products this applies at once; for rikma products it is a term).
descrip string اختياري
New description.

archiveRikmaProductTool

Archive a rikma product
  • يغيّر البيانات
  • قد يستبدل
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma id the product is listed in.
productId string إلزامي
Matanot id.
archived boolean إلزامي
true = archive. false (unarchive) is not done here — the tool returns the moach link.

setShopStockTool

Set shop stock
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

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

updateRikmaOrderStatusTool

Update order status
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

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

proposeProductEditTool

Propose a product edit
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

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

proposeProductEditsBatchTool

Propose product edits (batch)
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
items object[] إلزامي

setProductImagesTool

Set product pictures
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string إلزامي
Matanot id, from listRikmaProducts.
coverId string اختياري
Upload id of the cover picture.
galleryIds string[] اختياري
Upload ids after the cover, in order. [] clears the gallery but the cover.
variants object[] اختياري
Per-variant pictures.

upsertProductOptionsTool

Create or extend product options
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
options object[] إلزامي

upsertProductVariantsTool

Create or update product variants
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string إلزامي
Matanot id, from listRikmaProducts.
variants object[] إلزامي
reason string اختياري
Why — shown to the partners when something is proposed.

setProductCategoriesTool

Set product categories
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string إلزامي
Matanot id, from listRikmaProducts.
categoryIds string[] إلزامي

createRikmaProductsBatchTool

Create products (batch)
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
items object[] إلزامي

createUploadSessionTool

Create a picture upload link
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
productId string اختياري
The product the pictures are for (shown on the page; attaching is still setProductImages).
maxFiles integer اختياري
How many pictures the link accepts. Default 10.

uploadMediaFromUrlTool

Upload a picture from a URL
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id, from findUserProjectsTool. You must be a member.
url string اختياري
Public http(s) URL of the picture.
base64 string اختياري
The picture as base64 or a data: URL. Use url or base64, not both.
fileName string اختياري
A name for the stored file.

بانتظار الموافقة

تضع شيئًا عند عضو آخر، ويبقى بانتظار موافقته.

proposeProjectLinkTool

Propose a rikma link
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.
kind "website" | "github" | "drive" | "discord" | "facebook" | "x" | "whatsapp" إلزامي
Which link to set.
url string إلزامي
The URL. Pass an empty string to clear the link.

createTaskTool

Propose a task
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
ID of the project where the task will be created
name string إلزامي
Short name/title of the task
description string اختياري
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 اختياري
Optional URL related to the task
assignedUserId string اختياري
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[] اختياري
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 اختياري
ID of the mission in progress (mesimabetahaliches) this task belongs to, from getMemberMissionsTool. Goes with assignedUserId.
hashivut "white" | "green" | "yellow" | "red" اختياري
Urgency level of the task
dateS string اختياري
Start date (ISO format)
dateF string اختياري
End date (ISO format)

applyToMissionTool

Apply to an open mission
  • يغيّر البيانات

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.

المدخلات
openMissionId string إلزامي
The open mission id.
confirmedWithUser boolean إلزامي
true only after the user heard the mission name, hours and rate and said yes.
customerSignatureUnderstood boolean اختياري
true only after the user was told the deal's customers must also sign, and still wants to apply.

تواصل

مرئي للآخرين باسمك، ولا يُلزم أحدًا.

postConversationMessageTool

Post to a conversation
  • يغيّر البيانات

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.

المدخلات
forumId string إلزامي
Forum id, from listMyConversations.
message string إلزامي
The message, in the user's own words and language. Plain text.

openRikmaConversationTool

Open the rikma conversation
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.

startProcessTool

Start a process
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.
name string إلزامي
Short name, e.g. "Approach: city community centre".
description string اختياري
The raw text, in the user's own words: what this is, who it involves, what is hoped for.

attachToProcessTool

Attach to a process
  • يغيّر البيانات
  • لأعضاء الريكما فقط

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.

المدخلات
projectId string إلزامي
Rikma (project) id.
processId string إلزامي
Process id, from listRikmaProcesses or startProcess.
entityType "openMission" | "openMashaabim" | "mesimabetahalich" | "maap" | "pendm" | "pmash" إلزامي
What kind of object is being attached.
entityId string إلزامي
Id of that object.
name string اختياري
Its name, for the process timeline.

كتابة مشتركة

تنشئ التزامات على أشخاص آخرين. معطّلة ما لم يُمنح المفتاح صلاحية mcp:write.

createMissionTool

Create an open mission
  • يغيّر البيانات
  • لأعضاء الريكما فقط
  • يحتاج صلاحية 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.

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

الخصوصية

رغبة جديدة