home.social

Search

14 results for “openela”

  1. Bytes Europe @[email protected]

    OpenClaw creator spent $10 million on AI tokens last month byteseu.com/2474015/ #AI #ArtificialIntelligence #Language:EN #NewsBrief #StoryType:news

    #storytype #newsbrief #language #artificialintelligence #ai
  2. Christoph Schmees @[email protected]

    OpenClaw: Trojanische Skills

    Über böswillige Skills für OpenClaw habe ich schon berichtet, zuletzt hier (darin Links zu weiteren Meldungen). Solche trojanischen Skills werden auch über das öffentliche Repository ClawHub verbreitet. Ein Sicherheitsunternehmen hat jetzt eine Analyse vorgelegt, wie weit ein bestimmter Crypto-Miner (genannt clawrtc) immer noch verbreitet und aktiv ist. Zum Biotop des Schädlings gehören auch etliche Websites. Manche sind gehackte legitime Sites, manche wurden gezielt für schädliche Zwecke angelegt. Die Lehre aus den Befunden: Open-Source allein ist noch kein Schutz, auch nicht in der KI. Das Risiko, dass Cybergangster ihre Schädlinge in die Lieferkette einschleusen, ... Weiterlesen:

    pc-fluesterer.info/wordpress/2

    #banking #cybercrime #KI #krypto #trojaner

    #banking #cybercrime #ki #krypto #trojaner
  3. Dev Community @[email protected]
    OpenClaw (formerly Moltbot, with Clawdbot still used in parts of the community) is growing fast. The...#agents #ai #opensource #software #coding #development #engineering #inclusive #community
    What messaging apps does OpenClaw (Moltbot/Clawdbot) support?
    #agents #inclusive #engineering #development #coding #software
  4. Florencio Cano @florenciocano

    OpenClaw Security Audit openclaw.ai/blog/openclaw-trai

  5. Arint - SEO+KI @[email protected]

    RT @TheGeorgePu: OpenClaws Schöpfer hat letzten Monat 10 Millionen Dollar an Token verbrannt.

    mehr auf Arint.info

    #Ingenieurwesen #KI #Kosteneffizienz #KünstlicheIntelligenz #OpenClaw #Token #arint_info

    https://x.com/TheGeorgePu/status/2113335863623233612

    #ingenieurwesen #ki #kosteneffizienz #kunstlicheintelligenz #openclaw #token
  6. Rad Web Hosting | radwebhosting.com @[email protected]

    Updated Post: 🚀 Deploy Self-Hosted OpenClaw on VPS (3 Minute Quick-Start Guide 🤖)
    #Cloud #Guides #VPS

    🚀 Deploy Self-Hosted OpenClaw ...

    #cloud #guides #vps
  7. selfhost.directory @[email protected]

    📢 New #updates · 22 Oct #11

    · openclaw v2026.10.6 — Node runtime patched for security
    · OpenDesign open-design-v0.26.1
    · Wekan v12.61 — npm dependencies updated
    · lightdash 3.28.0 — Custom charts now point to Chart Studio
    · Password Pusher v2.16.0 — Added Prometheus metrics
    · Libredesk v2.9.0 — WhatsApp inbox integration

    More self-hosted updates → selfhost.directory?utm_source=

    #homeserverlife #api #security #git

    #updates #homeserverlife #api #security #git
  8. BjoernAusGE @[email protected]

    Tja wenn man irgendetwas selber könnte müsste man nicht 10 Millionen Dollar für Token ausgeben. Also mir wäre das peinlich. https://www.golem.de/news/ki-kosten-openclaw-gruender-gab-zehn-millionen-dollar-an-token-im-monat-aus-2610-214410.html
    #openai #openclaw #petersteinberger

    #petersteinberger #openclaw #openai
  9. Ireland @[email protected]

    europesays.com/ie/745863/ OpenClaw creator says he spent $10 million in tokens last month #AI #ArtificialIntelligence #ArtificialIntelligence #Éire #IE #Ireland #Technology

    #ai #artificialintelligence #eire #ie #ireland #technology
  10. România @[email protected]

    europesays.com/ro/341699/ Galaxy Buds On apar în listări europene: căștile clip-on Samsung ar costa peste undeva pe la 1.100 de lei #Android #CastiWireless #ClipOn #GalaxyAI #GeminiLive #OpenEar #RO #Română #Romania #Romanian #samsung #SamsungGalaxyBudsOn #SamsungGalaxyBuds4Pro #Technology #tehnologie

    #android #castiwireless #clipon #galaxyai #geminilive #openear
  11. Linux Magazine @linuxmagazine

    ICYMI: The latest release of the OpenAtom Foundation's openKylin features an upgrade to Linux 7.0 kernel, groundwork for post-quantum cryptography, and expanded AI integration.

    linux-magazine.com/Online/News

    #openatom #openkylin #enterpriselinux #ai #kylinbot #rust
  12. 🍁 Martin Guay 👨‍💻🌈🎮📱 @[email protected]

    The best translation tech is the kind that lets a conversation flow. Does Timekettle LiveTalk manage it? My review looks at the open-ear design, 25 offline language pairs, reported delays and the monthly translation limit. #AITranslation #OpenEar #TravelTech #Timekettle

    cryovex.com/timekettle-livetal

    #aitranslation #traveltech #timekettle #openear
  13. appgefahren.de - Tech-Blog @[email protected]

    In unserem aktuellen #Gewinnspiel gibt es nicht nur einen #BaseusBowieMC2 Open-Ear- #Kopfhörer. Wir verlosen an diesem Wochenende gleich zwei Exemplare im Wert von jeweils 59,99 Euro. Ihr dürft euch über ein Doppelpack der Kopfhörer in Schwarz und Blau freuen. Einen MC2 könnt ihr selbst behalten, den anderen könnt ihr verschenken und so die Freude teilen. Was kann es da noch Schöneres geben?

    Zur Verlosung: appgefahren.de/?p=407387

    #appgefahren #Apple #AppleBlog #Tech #TechBlog #iPhone #iPad #Mac #Baseus #OpenEar

    #gewinnspiel #baseusbowiemc2 #kopfhorer #appgefahren #apple #appleblog
  14. Dev Community @[email protected]

    Most AI agents can now talk to remote MCP servers. Apify runs one at https://mcp.apify.com, and any public Actor in Apify Store can be exposed through it as a tool your agent can call: SSL checks, DNS audits, broken-link crawls, screenshots, keyword research and thousands more.

    This post shows what actually happens on the wire, with a ~50-line stdlib Python client, so you can see exactly what your agent sees and pays for.

    1. Pick the tools with the URL


    ?tools= takes a comma-separated list of Actors:

    mcp.apify.com?tools=datawright…

    Auth is your Apify API token as Authorization: Bearer <APIFY_TOKEN> (free account; Actors bill per result on your own account).

    2. The client


    """Call Apify Store Actors as MCP tools from plain Python (stdlib only).
    Usage: APIFY_TOKEN=... python3 mcp_agent_tools.py
    """
    import json, os, urllib.request

    TOOLS = "datawright-labs/ssl-certificate-checker,datawright-labs/email-domain-dns-checker"
    URL = f"https://mcp.apify.com?tools={TOOLS}"
    HEADERS = {
    "Authorization": "Bearer " + os.environ["APIFY_TOKEN"],
    "Content-Type": "application/json",
    "Accept": "application/json, text/event-stream",
    }

    def rpc(body, session=None):
    h = dict(HEADERS)
    if session:
    h["mcp-session-id"] = session
    req = urllib.request.Request(URL, data=json.dumps(body).encode(), headers=h)
    with urllib.request.urlopen(req, timeout=180) as r:
    text = r.read().decode()
    sid = r.headers.get("mcp-session-id") or session
    # Streamable HTTP may answer as SSE ("data: {...}") or plain JSON
    msgs = [json.loads(l[5:]) for l in text.splitlines() if l.startswith("data:")]
    return (msgs[-1] if msgs else (json.loads(text) if text.strip() else None)), sid

    # 1. Handshake
    _, sid = rpc({"jsonrpc": "2.0", "id": 1, "method": "initialize",
    "params": {"protocolVersion": "2025-03-26", "capabilities": {},
    "clientInfo": {"name": "tutorial", "version": "1"}}})
    rpc({"jsonrpc": "2.0", "method": "notifications/initialized"}, sid)

    # 2. What tools does the agent see?
    tools, _ = rpc({"jsonrpc": "2.0", "id": 2, "method": "tools/list"}, sid)
    for t in tools["result"]["tools"]:
    print(f"- {t['name']}: {t.get('description', '')[:90]}")

    # 3. Call one, exactly like an agent would
    name = next(t["name"] for t in tools["result"]["tools"] if "ssl-certificate-checker" in t["name"])
    res, _ = rpc({"jsonrpc": "2.0", "id": 3, "method": "tools/call",
    "params": {"name": name, "arguments": {"domains": ["example.com", "github.com", "expired.badssl.com"]}}}, sid)
    for c in res["result"]["content"]:
    print(c.get("text", "")[:1500])

    # 4. The call returns a run summary; the rows come from get-dataset-items (the agent's next step)
    run = json.loads(res["result"]["content"][0]["text"])
    ds = run["storages"]["datasets"]["default"]["id"]
    items, _ = rpc({"jsonrpc": "2.0", "id": 4, "method": "tools/call",
    "params": {"name": "get-dataset-items",
    "arguments": {"datasetId": ds, "limit": 20,
    "fields": "host,status,daysUntilExpiry,issuerOrganization,problems"}}}, sid)
    for c in items["result"]["content"]:
    print(c.get("text", "")[:2000])

    3. What the agent sees


    tools/list returns one tool per Actor (datawright-labs--ssl-certificate-checker, datawright-labs--email-domain-dns-checker) plus four helpers: get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run.

    4. The two-step call (the part most guides skip)


    Calling the Actor tool runs it and returns a run summary, not the rows: status, run time, item count, the field list and a nextStep hint telling the agent to call get-dataset-items. Good agents follow that hint; if yours stops at "SUCCEEDED", tell it to fetch the dataset items. Passing fields= keeps the tokens down:

    {"host":"example.com","status":"ok","daysUntilExpiry":63,"problems":[]}
    {"host":"github.com","status":"ok","daysUntilExpiry":37,"problems":[]}
    {"host":"expired.badssl.com","status":"expired","daysUntilExpiry":-4212,"problems":["Certificate expired","Not trusted: CERT_HAS_EXPIRED"]}

    That whole round trip took about 9 seconds and cost $0.003 (3 hosts at $1 per 1,000).

    5. Plug the same URL into your agent


    Any client that supports remote Streamable HTTP MCP servers with a header takes the same two values (URL + Bearer header). Two configs we tested end to end for connection and tool discovery:

    • Hermes (pip install "hermes-agent[mcp]"), ~/.hermes/config.yaml: mcp_servers: { datawright: { url: "...", headers: { Authorization: "Bearer ${APIFY_TOKEN}" } } }, then hermes mcp test datawright.
    • OpenClaw: openclaw mcp add datawright --no-probe --url "..." --transport streamable-http --header 'Authorization=Bearer ${APIFY_TOKEN}', then openclaw mcp probe datawright (the pre-save probe doesn't expand ${APIFY_TOKEN}, hence --no-probe).


    6. Gotchas


    • Agents only see the top 10 results of Apify's search-actors, so pin the Actors you want with ?tools= instead of letting the agent search.
    • /sse is gone; use the Streamable HTTP endpoint above.
    • Keep the token in an env var or your client's secret store, never in a prompt.

    Disclosure: the two example Actors are ours (Datawright Labs). Any Store Actor works the same way.#ai #mcp #python #tutorial #software #coding #development #engineering #inclusive #community
    Give your AI agent web-data tools with Apify's MCP server (Python, no SDK, 2026)

    #ai #community #software #coding #python #development
Share on Mastodon

Enter the server where you have an account.