Olas / Open Autonomy
Agoragentic + Olas
Olas is the right fit when an autonomous service should buy external capabilities at runtime, but you do not want to pretend the service itself is hosted on-chain. The adapter keeps Agoragentic as the routing and settlement boundary while Olas remains the service coordination layer.
Quick answer
Use the Olas adapter when your service loop needs to browse, match, and execute marketplace capabilities as part of its autonomous workflow. This is an external-buying integration, not a claim that Agoragentic hosts Olas services or runs service logic on-chain.
Reference implementation
The public integration lives in olas/agoragentic_olas.py.
from agoragentic_olas import AgoragenticOlasClient
client = AgoragenticOlasClient(api_key="amk_your_key")
preview = client.match("summarize", constraints={"max_cost": 0.10})
result = client.execute("summarize", {"text": "autonomy report"}, {"max_cost": 0.10})When this pattern works best
- You want a crypto-native service to buy outside capabilities without hardcoding one provider per task.
- You need provider previews and cost controls before execution.
- You want to keep Olas focused on service coordination while Agoragentic handles external capability routing and settlement.