MCP pentru AI

Conecteaza asistenti de IA la spatiul tau de lucru pentru retele sociale

Styrar include un server Model Context Protocol (MCP) nativ - conecteaza Claude, Cursor, n8n sau orice instrument de IA compatibil MCP in cateva minute folosind o cheie API sau OAuth. Inteligenta ta artificiala lucreaza direct cu postarile, linkurile, conturile si analizele tale reale. Fara pluginuri, fara conectori terti, fara configurare suplimentara.

Vedeți toate funcționalitățile

Ce poate face AI-ul tau cu Styrar

Instrumente expuse prin MCP:

  • `list_posts` - preia postarile programate, publicate si in ciorna cu filtre
  • `create_post` - creeaza o ciorna noua cu tintire pe platforma si media
  • `get_link_analytics` - preia datele de clicuri si performanta campaniilor pentru o perioada
  • `list_links` - preia linkurile scurte si performanta campaniilor
  • `create_link` - creeaza un link scurt de brand cu parametri UTM
  • `list_social_accounts` - listeaza conturile sociale conectate si statusul lor
  • `search` - cauta postari, linkuri si campanii in spatiul de lucru

Colecția completă de instrumente

Fiecare acțiune de mai jos poate fi apelată de asistentul tău AI prin MCP — organizată pe categorii.

147tools across 12 categories
Links & social accounts29
  • list_social_accountsList connected Instagram, X (Twitter), TikTok, LinkedIn, YouTube, Threads, Facebook, and other social accounts. Optional companyId for company scope.
  • create_linkCreate a shortened URL with optional title, shortCode, company scope, expiresAt, activeFrom, campaignIds, linkGroupId, tagIds, customDomainId, qrStyle, and custom OG fields (ogTitle, ogDescription, ogImageUrl, ogInterstitialEnabled).
  • list_linksList shortened URLs; filter by companyId, campaignId, linkGroupId, tagId, or unassigned (no campaign).
  • get_linkFetch a single short link by linkId including click count and campaign metadata.
  • update_linkUpdate a short link: originalUrl, title, isActive, activeFrom, expiresAt, campaignId/campaignIds, linkGroupId, tagIds, qrStyle, and custom OG fields.
  • delete_linkPermanently delete a short link by linkId.
  • list_link_groupsList link groups (folders) for personal or company scope.
  • create_link_groupCreate a link group/folder with title and optional companyId or campaignId.
  • update_link_groupRename a link group by groupId.
  • delete_link_groupDelete a link group; links in the folder become unassigned.
  • list_link_tagsList tags used to label short links in personal or company scope.
  • create_link_tagCreate a link tag by name in personal or company scope.
  • update_link_tagRename a link tag by tagId.
  • delete_link_tagDelete a link tag and remove it from assigned links.
  • list_link_routing_rulesList geo/device routing rules that redirect visitors to alternate destination URLs.
  • create_link_routing_ruleAdd a geo or device rule mapping conditions to an HTTPS destinationUrl.
  • update_link_routing_ruleUpdate priority, conditions, destination URL, or active state on a link routing rule.
  • delete_link_routing_ruleRemove a geo/device routing rule from a short link.
  • get_link_experimentFetch the A/B experiment on a short link (variants, weights, status, click counts).
  • update_link_experimentCreate or replace a draft link experiment with HTTPS destinationUrl variants and weights.
  • delete_link_experimentRemove the A/B experiment configuration from a short link.
  • control_link_experimentStart, pause, or complete a link A/B experiment. Pass winningVariantId when completing.
  • bulk_create_linksCreate up to 100 links from a links array or CSV string. Set upsert true for idempotent shortCode imports.
  • bulk_update_linksUpdate up to 100 links in one request via an updates array (each entry needs id).
  • bulk_delete_linksDelete multiple short links by linkIds in personal or company scope.
  • import_link_ogScrape og:title, og:description, and og:image from the link destination URL into custom OG fields.
  • get_link_qrReturn short link QR metadata (shortCode, qrStyle). Binary PNG/SVG download uses the dashboard or GET /v1/links/:id/qr.
  • get_link_analyticsAggregated click counts across all short links; optional companyId and date range (from, to).
  • get_link_analytics_by_idClick analytics for a single linkId; optional date range (from, to).
Posts9
  • create_postCreate a DRAFT or SCHEDULED social post across Instagram, LinkedIn, X, TikTok, YouTube, and more. Use scheduledAt to schedule—no separate schedule_post tool. Call list_social_accounts first for socialAccountId in each target.
  • list_postsList posts with optional filters—status (DRAFT, SCHEDULED, PUBLISHED, FAILED), companyId, date range (from, to), page, limit.
  • get_postFetch a single post by postId including platform targets, approval status, media files, and analytics.
  • update_postUpdate a DRAFT or SCHEDULED post by postId. Editable fields: content, title, scheduledAt, status, campaignId, brandId, tags, mediaFileIds.
  • delete_postPermanently delete a post by postId (must be DRAFT, SCHEDULED, or FAILED).
  • list_saved_mentionsList workspace saved @mentions with per-platform handles for compose and publish substitution.
  • create_saved_mentionCreate or upsert a saved @mention with optional per-platform handles (X, LinkedIn, etc.).
  • update_saved_mentionUpdate a saved mention name or platformHandles by mentionId.
  • delete_saved_mentionDelete a workspace saved mention by mentionId.
Bio pages54
  • list_bio_pagesList bio pages for personal or company scope; includes live version and custom domain metadata.
  • get_bio_pageFetch one bio page by id, including live blocks and custom domain details.
  • create_bio_pageCreate a new bio page with title and optional company scope.
  • update_bio_pageUpdate bio page settings: title, custom tenantSlug, allowCustomSlug, trackingConfig (GA/GTM/pixels), and cookiePolicy banner when tracking is enabled.
  • delete_bio_pageDelete a bio page and linked sentinel click-tracking link.
  • list_bio_versionsList versions for a specific bio page id.
  • create_bio_versionSave a new bio page version draft with theme, pages, pageMeta, and chrome blocks. Set copyFromSource true to clone the latest locale version.
  • delete_bio_versionDelete a saved bio version. Cannot delete the only version on a page.
  • publish_bio_versionPublish a specific version id as the live bio page.
  • get_bio_blocksList blocks for a bio page version, optionally filtered by pagePath.
  • replace_bio_blocksReplace chrome blocks for a bio version (hero, nav, footer). For section content use update_bio_version.
  • get_bio_versionFetch a bio version with theme, pages, pageMeta sections, and chrome blocks. Omit versionId for the latest locale draft.
  • update_bio_versionSave a bio draft in place with theme, pages, pageMeta (sections), and chrome blocks. Use for layout and content edits.
  • get_bio_experimentFetch the A/B experiment config for a bio page (variants, scope, status, click counts).
  • update_bio_experimentCreate or replace a draft bio experiment with variants (bioPageVersionId + weight). Scope: page, section, or block.
  • delete_bio_experimentRemove the A/B experiment configuration from a bio page.
  • control_bio_experimentStart, pause, or complete a bio A/B experiment. Pass winningVariantId when completing.
  • list_bio_routing_rulesList geo/device routing rules that serve alternate bio versions to visitors.
  • create_bio_routing_ruleAdd a geo or device routing rule mapping conditions to a bioPageVersionId.
  • update_bio_routing_ruleUpdate priority, conditions, target version, or active state on a bio routing rule.
  • delete_bio_routing_ruleRemove a geo/device routing rule from a bio page.
  • get_bio_domainFetch the custom domain attached to a bio page (company workspaces only).
  • set_bio_domainAttach a custom hostname to a bio page. Returns DNS records to configure.
  • verify_bio_domainRe-check Cloudflare verification status for a bio page custom domain.
  • delete_bio_domainDetach and delete the custom domain from a bio page.
  • list_bio_blog_categoriesList blog categories for a bio page, optionally filtered by locale.
  • create_bio_blog_categoryCreate a blog category on a bio page with name, locale, and optional slug.
  • update_bio_blog_categoryUpdate a bio blog category name or slug.
  • delete_bio_blog_categoryDelete a bio blog category.
  • list_bio_blog_postsList blog posts on a bio page; filter by locale, status, or categoryId.
  • get_bio_blog_postFetch one bio blog post by id.
  • create_bio_blog_postCreate a bio blog post with title, HTML content, excerpt, cover image, SEO fields, and DRAFT or PUBLISHED status.
  • update_bio_blog_postUpdate bio blog post content, metadata, category, slug, or publish status.
  • delete_bio_blog_postDelete a bio blog post.
  • get_bio_booking_settingsFetch appointment booking settings for a bio page: timezone, notice windows, deposit processor (Stripe or Shopify), calendar sync, and notification email.
  • update_bio_booking_settingsConfigure bio booking: IANA timezone, notifyEmail, minNoticeMinutes, maxAdvanceDays, depositProcessor with stripeConnectAccountId or shopifyStoreId, and optional calendar sync fields.
  • list_bio_booking_servicesList bookable services on a bio page with duration, buffer, capacity, custom fields, and optional deposit amounts.
  • get_bio_booking_serviceFetch one bio booking service by bioPageId and serviceId.
  • create_bio_booking_serviceAdd a bookable service with name, durationMinutes, optional description, buffer, capacity, custom intake fields, and optional depositAmountCents.
  • update_bio_booking_serviceUpdate service name, duration, deposits, custom fields, active state, or sort order.
  • delete_bio_booking_serviceRemove a bookable service from a bio page.
  • list_bio_booking_availability_rulesList weekly hours and date-override availability or blackout rules for bio booking.
  • create_bio_booking_availability_ruleAdd weekly hours or a date_override rule. Use ruleType weekly with weekday 0-6, or date_override with YYYY-MM-DD. Set isBlackout for blocked days.
  • update_bio_booking_availability_ruleUpdate startMinute/endMinute, blackout flag, or date on an availability rule.
  • delete_bio_booking_availability_ruleRemove a weekly or date-override availability rule.
  • list_bio_booking_appointmentsList upcoming or past appointments for a bio page with optional limit and cursor pagination.
  • get_bio_booking_appointmentFetch one appointment with service, slot times, guest details, and status.
  • update_bio_booking_appointmentMark a confirmed past appointment as no_show via action no_show.
  • cancel_bio_booking_appointmentCancel a confirmed appointment and notify the guest when configured.
  • list_bio_theme_presetsList workspace-saved custom bio theme presets for personal or company scope.
  • create_bio_theme_presetSave a reusable bio theme preset with label and theme JSON for the active workspace.
  • delete_bio_theme_presetDelete a saved custom bio theme preset by presetId.
  • get_bio_analyticsFetch click analytics for a bio page id with optional from/to date range.
  • get_workspace_bio_analyticsOverview analytics across all bio pages in personal or company scope.
Campaigns5
  • list_campaignsList campaigns for personal or company scope with optional brand and click totals filters.
  • get_campaignFetch one campaign by id including counts and brand metadata.
  • create_campaignCreate a campaign with name and optional company, brand, destination, UTM, and dynamic link settings.
  • update_campaignUpdate a campaign by campaignId. Editable fields: name, description, defaultDestinationUrl, dynamicSourceEnabled, dynamicLinkMode, utmDefaults, brandId.
  • delete_campaignPermanently delete a campaign by campaignId.
Content planning8
  • get_content_planning_boardFetch the company content pipeline board and work items. Use view kanban for /content/plan column order, list for /content/list sorting, or timeline for /content/timeline due-date ranges. Requires company workspace and contentPlanning feature flag. Filters: campaignId, brandId, stage slug/id, tag, assigneeUserId, type (POST|LINK|BIO_UPDATE), q. Timeline view accepts optional from/to ISO dates (defaults to current month through two months ahead).
  • create_content_work_itemAdd a card to the content planning pipeline (Kanban). Requires companyId. Optional stageId, type (POST|LINK|BIO_UPDATE), title, description, campaignId, brandId, assigneeUserId, startDate, endDate, dueDate, linked postId/linkId/bioPageId, and tags.
  • update_content_work_itemUpdate a planning card by workItemId and companyId. Editable fields match create_content_work_item plus stageId and position.
  • delete_content_work_itemPermanently delete a planning card by workItemId and companyId.
  • move_content_work_itemMove a planning card to another pipeline stage (Kanban column). Requires workItemId, companyId, stageId; optional position within the column.
  • add_content_work_item_tagAdd a tag label to a planning card. Requires workItemId, companyId, and tag.
  • remove_content_work_item_tagRemove a tag from a planning card. Requires workItemId, companyId, and tag.
  • reorder_content_planning_stagesReorder or rename Kanban pipeline stages. Requires content_planning:admin. Pass companyId, boardId, and stages array with id plus optional position and name.
Automations8
  • list_automationsList automation flows for personal or company scope.
  • get_automationFetch one automation by id including recent runs and nodes.
  • create_automationCreate an automation with name and optional description or company scope.
  • update_automationUpdate automation fields such as name, description, status, or viewport coordinates.
  • list_automation_runsList run history for a specific automation id.
  • run_automationTrigger a manual run for an automation with optional input payload.
  • create_automation_nodeAdd a step to an automation (kind, label, x, y required) with optional visual and config fields.
  • create_automation_edgeConnect two automation steps with a link between them.
Approval flows7
  • list_approval_flowsList approval flows for a company (companyId required).
  • get_approval_flowFetch one approval flow by id including nodes and edges.
  • create_approval_flowCreate a company approval flow with name, optional description, and optional default flag.
  • update_approval_flowUpdate approval flow fields such as name, description, status, and default flag.
  • delete_approval_flowDelete an approval flow by id.
  • test_approval_flowSimulate a flow test run with optional dummy post fields and get step and notification results.
  • post_approval_actionPerform post approval actions (approve, reject, request_changes, reassign, override) on post tasks.
AI skill documents6
  • list_skill_documentsList Markdown skill documents for the current user or a specific brand (provide both companyId and brandId for brand scope). Returns id, slug, title, sortOrder.
  • get_skill_documentFetch a single skill document by id, including the full Markdown body. Optionally scope to a brand with companyId + brandId.
  • create_skill_documentCreate a new Markdown skill document for the user or a brand (provide both companyId and brandId for brand scope). Use list_skill_templates to get ready-made starting content.
  • update_skill_documentUpdate an existing skill document's title, Markdown body, slug, or sortOrder by id.
  • delete_skill_documentDelete a skill document by id. Optionally scope to a brand with companyId + brandId.
  • list_skill_templatesList ready-made Markdown templates — brand voice, Instagram strategy, LinkedIn strategy, content calendar, campaign planner, and hashtag strategy. Copy a template body into create_skill_document to add it to a workspace.
Media library6
  • upload_mediaStore an image in the media library by passing its content as a base64-encoded string (fileData). Requires fileName and mimeType (must be image/*). The file is stored securely in S3 and automatically processed. Returns the stored file id and a signed view URL. Use when the user sends an image directly in the conversation.
  • upload_media_from_urlFetch a public image URL and store it in the media library. Requires url (must resolve to an image). Optional fileName and companyId. Returns the stored file id and a signed view URL.
  • generate_imageGenerate a new image from a text prompt and save it to the media library. Requires prompt. Optional fileName, companyId, provider (openai or gemini), and size (1024x1024, 1536x1024, or 1024x1536). Returns the stored file id and signed viewUrl.
  • list_mediaReturns the 25 most recent images and videos from the media library as an interactive picker with inline previews. Images are shown directly; videos are shown with their thumbnail frame. Each item includes fileName, id, mimeType, sizeBytes, and duration (for videos). Call this whenever the user needs to choose a media file. Optional filters: companyId, q (filename search), tag, page.
  • get_mediaFetch a single library file by id, including a signed view URL and processing status.
  • delete_mediaPermanently delete a library file by id. The file is removed from S3 and the account.
Companies & brands9
  • list_companiesList all companies the authenticated user belongs to, with role and member counts. Call this first to discover available companyId values.
  • get_companyFetch a single company by id including brand count, member count, and subscription plan.
  • create_companyCreate a new company workspace with a name and unique slug. The authenticated user becomes the owner.
  • update_companyUpdate a company's name or other profile fields by companyId.
  • list_brandsList all brands for a company by companyId. Returns id, name, slug, isArchived, and logo. Call before scoping posts, campaigns, or skill documents to a brand.
  • get_brandFetch a single brand by companyId and brandId including guidelines and logo.
  • create_brandCreate a new brand inside a company by companyId. Requires a name; slug is auto-derived.
  • update_brandUpdate a brand's name, guidelines, or archive status by companyId and brandId.
  • list_company_membersList members of a company by companyId. Returns user name, email, role, and brand access. Useful for approval flow setup.
Workspace notes5
  • list_notesList workspace notes for personal or company scope. Optional companyId to filter to a company workspace.
  • get_noteFetch a single workspace note by noteId including full body text.
  • create_noteCreate a markdown workspace note with title and body. Optional companyId and visibility (PRIVATE or COMPANY).
  • update_noteUpdate a workspace note's title, body, or visibility by noteId.
  • delete_notePermanently delete a workspace note by noteId.
Search1
  • searchGlobal search across posts, links, campaigns, bio pages, and notes. Returns matched items with type labels. Use for broad 'find me something' queries.

Conecteaza-te in cateva minute

Claude Desktop

  1. Deschide panoul Styrar → Setari → Chei API → Genereaza cheie noua
  2. Deschide Claude Desktop → Setari → Developer → Editeaza config
  3. Adauga blocul server MCP Styrar de mai jos in `claude_desktop_config.json`
  4. Reporneste Claude Desktop. Intreaba Claude: "Ce postari am programate saptamana aceasta?"
{
  "mcpServers": {
    "styrar": {
      "type": "streamable-http",
      "url": "https://mcp.styrar.com",
      "headers": {
        "Authorization": "Bearer your_api_key_here"
      }
    }
  }
}

Cursor / HTTP la distanta

  1. Deschide panoul Styrar → Setari → Chei API → Genereaza cheie noua
  2. In Cursor Setari → MCP → Adauga server cu URL-ul si antetul Authorization de mai jos
  3. Cursor va descoperi automat instrumentele disponibile. Incepe sa folosesti prompturi.
  • URL: https://mcp.styrar.com
  • Header: Authorization: Bearer your_api_key_here

Exemple de prompturi

  • Care sunt postarile mele cu cea mai buna performanta din luna trecuta?
  • Creeaza o ciorna pentru Instagram care anunta lansarea noului nostru produs
  • Cate clicuri a primit linkul meu styrar.link/launch saptamana aceasta?
  • Programeaza o postare LinkedIn pentru maine la ora 9
  • Care este rata mea de engagement pe toate platformele luna aceasta?

Ce deblocheaza Styrar MCP pentru echipa ta

Server MCP nativ inclus

Fara pluginuri sau conectori terti. Styrar expune un endpoint MCP conform standardelor pe care il conectezi cu o cheie API sau OAuth - disponibil in planurile Team si Agency.

Functioneaza cu Claude, Cursor, n8n si altele

Orice client compatibil MCP se poate conecta. Claude Desktop, Cursor, n8n si agentii personalizati functioneaza imediat cu acelasi endpoint de server si aceeasi autentificare.

Permisiunile sunt mostenite automat

Inteligenta ta artificiala opereaza in cadrul rolurilor si capacitatilor exacte pe care le-ai configurat pentru spatiul tau de lucru. Nu poate publica, sterge sau accesa nimic ce nu ai permis deja.

Planifica, analizeaza si gestioneaza prin limbaj natural

Cere asistentului tau de IA sa redacteze si sa programeze o postare, sa obtina analizele saptamanii trecute, sa creeze un link scurt sau sa listeze conturile tale conectate. Apeleaza direct instrumentele Styrar si returneaza rezultate in context.

Conectat in mai putin de cinci minute

Serverul MCP al Styrar functioneaza prin HTTP si se autentifica prin token Bearer sau OAuth. Genereaza o cheie API in Setari - Chei API, lipeste URL-ul serverului si tokenul in clientul tau de IA si esti gata. Fara server local, fara Docker, fara etapa de compilare.

  • Genereaza o cheie APIDeschide Setari - Chei API in tabloul de bord Styrar si creeaza o cheie noua cu permisiunile de care ai nevoie.
  • Adauga serverul MCP la clientul tauLipeste URL-ul endpoint-ului MCP al Styrar si cheia ta API in Claude Desktop, Cursor sau clientul MCP preferat.
  • Incepe sa lucrezi cu IA-ul tauAsistentul tau de IA poate acum programa postari, obtine analize, gestiona linkuri si interoga conturile tale de retele sociale direct din chat sau IDE.

Ce poate face IA-ul tau prin Styrar MCP

Serverul MCP al Styrar expune un set complet de instrumente care acopera intregul flux de lucru al Social OS. IA-ul tau poate actiona in numele tau pentru programare, analize si gestionarea linkurilor, cu aceleasi garantii ca tabloul de bord.

  • Programeaza si redacteaza postariCere IA-ului tau sa creeze o postare programata pentru una sau mai multe platforme, sa seteze un timp de publicare si sa o puna in coada, fara a deschide tabloul de bord.
  • Obtine analize si date de performantaRecupereaza acoperire, engagement, numarul de clicuri pe linkuri si cresterea urmaritorilor pentru orice cont conectat sau interval de date.
  • Creeaza si gestioneaza linkuri scurteGenereaza linkuri scurte branduite, consulta analizele clicurilor si organizeaza linkurile in campanii prin limbaj natural.
  • Interogheaza conturile conectateListeaza conturile tale de retele sociale conectate, verifica limitele de postare sau intreaba ce platforme sunt active in spatiul de lucru curent.
  • Gestioneaza coada de continutRevizuieste, reprogrameaza sau anuleaza postari programate, util pentru editari in masa sau audituri de continut pre-lansare realizate de un agent IA.

Teams folosesc AI cu Styrar

Dezvoltatori din Cursor

Scrieți postări, extrageți analize și gestionați legăturile din IDE prin serverul MCP și cheia API.

Operatori din Claude

Cereți-i asistentului să pună în coadă conținutul sau să rezuma performanța fără a deschide o altă filă.

Agenții

Standardizați sarcinile sociale repetabile prin instrumente AI, în timp ce RBAC menține spațiile de lucru ale clientului separate.

Intrebari frecvente despre IA si MCP

Ce este MCP si cum il foloseste Styrar?

Model Context Protocol (MCP) este un standard deschis care permite asistentilor de IA sa apeleze instrumente externe in mod securizat. Styrar implementeaza un server MCP astfel incat clienti precum Claude si Cursor pot programa postari, citi analize si gestiona linkuri in spatiul tau de lucru. Te autentifici cu o cheie API sau OAuth, fara pluginuri sau middleware necesare.

Cum conectez Claude Desktop la Styrar?

Genereaza o cheie API in Setari - Chei API in Styrar, apoi adauga URL-ul serverului MCP al Styrar si cheia ta la configuratia Claude Desktop (claude_desktop_config.json). Reporneste Claude Desktop si asistentul tau va avea acces imediat la instrumentele spatiului tau de lucru Styrar.

Cum conectez Cursor la Styrar?

In Cursor, deschide Setari - MCP si adauga o noua intrare de server cu URL-ul endpoint-ului MCP al Styrar si cheia ta API ca token Bearer. Dupa salvare, Cursor Composer poate apela direct instrumentele Styrar.

Pot conecta n8n sau alte instrumente de automatizare?

Da. n8n suporta servere MCP in mod nativ prin nodul sau client MCP. Configureaza endpoint-ul MCP al Styrar si cheia ta API in credentialul n8n, apoi foloseste-l in orice flux de lucru.

IA-ul meu ocoleste fluxurile de aprobare?

Nu. Actiunile IA urmeaza aceleasi reguli de permisiuni si fluxuri de aprobare ca tabloul de bord. Daca spatiul tau de lucru necesita aprobarea postarilor inainte de publicare, o postare initiata de IA va intra in aceeasi coada de aprobare.

Conexiunea MCP este sigura?

Da. Tot traficul MCP trece prin HTTPS. Autentificarea foloseste o cheie API a tabloului de bord sau consimtamant OAuth, si poti revoca accesul oricand din Setari - Chei API.

Ce poate face IA-ul meu prin serverul MCP al Styrar?

Serverul MCP actual expune instrumente pentru programarea si redactarea postarilor, citirea analizelor si performantei linkurilor, crearea si gestionarea linkurilor scurte, listarea conturilor de retele sociale conectate si gestionarea continutului programat.

Integrarea MCP functioneaza cu ChatGPT?

ChatGPT suporta MCP prin sistemul sau de Actiuni, care foloseste un flux de configurare diferit fata de Claude sau Cursor. Poti directiona o Actiune ChatGPT personalizata catre endpoint-ul compatibil MCP al Styrar. Contacteaza asistenta pentru ghidul de integrare actual.

Adauga IA la fluxul tau de lucru social

Conecteaza Styrar la Claude, Cursor sau orice instrument de IA compatibil MCP. Dureaza aproximativ cinci minute.

Vedeți prețurile

Join the beta waitlist

By signing up you agree to receive marketing email. See our Privacy Policy.