Axon

1

6

87

Axon@axon402·2h

We've seen a growing number of projects reaching out regarding potential partnerships and integrations with Axon! It's exciting to see interest coming from different areas of the ecosystem, from AI agents and developer tooling to infrastructure and payment solutions. Our goal is simple: work with projects that can create meaningful value for developers building on Axon and help strengthen the network as a whole. We're looking forward to exploring what's possible.

English

1

15

310

Axon@axon402·4h

x402 making its way into agentic finance too. Agents paying for what they need, automatically, no subscriptions. This is what the protocol is for.

Coinbase 🛡️@coinbase

Meet Coinbase for Agents. Give your agent its own account to: → Execute trades & manage your portfolio → Run autonomously under guardrails → Pay for data & research tools via x402 (coming next week) Agentic finance is here, and it's powered by Coinbase.

English

2

10

431

Axon@axon402·6h

Tomorrow, we'll continue work on Phase 1 of the Axon roadmap and release configurable spend threshold alerts per agent wallet. Right now, there is no way to know when an agent is spending too much. You would only find out after the fact by checking balances manually. This update adds spend threshold monitoring directly into Axon itself. When an agent's spending exceeds a configured limit, the platform will detect it automatically. Thresholds will be configurable per agent wallet, and alerts will fire in real time when a limit is crossed. This creates the foundation for budget controls, automated spend protection, and future automated responses when limits are hit. The goal is simple: Move from manually checking balances to making overspending visible, configurable, and actionable from inside the platform. For more information: axon-agents.com/docs/roadmap

English

2

12

339

Axon@axon402·9h

Phase 1 - Error tracking integration for API routes, workers, and webhook delivery is DONE in Axon: Right now when something breaks in Axon. A payment fails, a task crashes, a webhook can't deliver. The error gets written to Railway logs and that's it. To find it we have to open Railway, scroll through hundreds of log lines, and search manually. There's no way to see if the same error is happening over and over, no way to filter by agent or time, nothing. After this update every error is saved to the database automatically the moment it happens. So we can query: show me all errors from the last hour, show me everything that failed for this specific agent, how many errors happened today vs yesterday. It's all there without touching Railway. 2/5 Sections done in Phase 1👀 github.com/SeierkDev/Axon…

English

2

12

473

Axon 已转推

Degen Ape@degenApe22·10h

I slept on my new PF shitter bag $AXON as I see something here I wake up to see the development accelerating yet pa doing the opposite, usual PF yeets It’s a micro cap shitter till proven otherwise but I’m liking what I see so far Super degen atm, but fug it we ball

Distributed tracing isn't a flashy feature. It's the infrastructure that lets Axon scale. A single task can move through APIs, workers, payments, webhooks, and multiple agents before reaching completion. Without tracing, diagnosing issues means digging through disconnected logs across the entire system. Distributed tracing gives every task a single lifecycle that can be followed end-to-end. You can see where time was spent, where failures occurred, how agents interacted, and where bottlenecks exist. As Axon grows, observability becomes essential. This is the kind of work that makes a protocol production-ready and capable of supporting real-world agent networks at scale.

English

4

5

13

1.1K

Axon@axon402·10h

@Ragnar110323 We keep it going👀

English

2

0

1

47

Ragnar@Ragnar110323·10h

@axon402 This it’s the attitude dev 💪 people will come when they will see huge potential The chart it’s important,yes, but a good and working utility will blow up the chart ,conf holding Thx you because you didn’t give up Keep it up

English

0

1

53

Axon@axon402·10h

Distributed tracing isn't a flashy feature. It's the infrastructure that lets Axon scale. A single task can move through APIs, workers, payments, webhooks, and multiple agents before reaching completion. Without tracing, diagnosing issues means digging through disconnected logs across the entire system. Distributed tracing gives every task a single lifecycle that can be followed end-to-end. You can see where time was spent, where failures occurred, how agents interacted, and where bottlenecks exist. As Axon grows, observability becomes essential. This is the kind of work that makes a protocol production-ready and capable of supporting real-world agent networks at scale.

We've now shipped distributed trace context propagation on Axon Every task now gets a trace ID at creation. Inherited from the HTTP request when available. It follows the task through the worker, payment settlement, and webhook queueing. All logs for a task chain share one ID. New files: - migrations/014_task_trace.sql - src/lib/tracing.ts - src/app/api/tasks/[taskId]/trace/route.ts: Modified files: - src/lib/tasks.ts - src/lib/logger.ts - src/workers/index.ts - src/sdk/types.ts - src/app/docs/roadmap/page.tsx Multi-agent workflows propagate the same trace ID across every step so you can follow a chain end to end in your logs. github.com/SeierkDev/Axon…

English

2

1

13

1.6K

Axon@axon402·11h

@Ragnar110323 We will!

English

0

1

63

Ragnar@Ragnar110323·11h

@axon402 Keep building 💪💪💪 we send back

English

0

1

85

Axon@axon402·11h

Axon have no positions on token $AXON. We dont impact the price. Will keep shipping regardless of the price. We are here long term. Lets get back to building.

English

6

2

15

494

Axon@axon402·11h

@MonsterTwists We keep building! Just the beginning.

English

0

1

85

No@MonsterTwists·11h

@axon402 the token gros will come as long as you keep cooking. i have 0 fear and dont care about the current price 🫡

English

0

1

98

Axon@axon402·13h

@MonsterTwists Basically means. Every task in Axon now gets one unique ID. That ID follows the task through every step, so all logs stay connected and you can see the full picture easily.

English

0

2

63

No@MonsterTwists·13h

@axon402 I dont understand shit but LFG !! 😆

English

3

0

3

77

Axon@axon402·13h

We've now shipped distributed trace context propagation on Axon Every task now gets a trace ID at creation. Inherited from the HTTP request when available. It follows the task through the worker, payment settlement, and webhook queueing. All logs for a task chain share one ID. New files: - migrations/014_task_trace.sql - src/lib/tracing.ts - src/app/api/tasks/[taskId]/trace/route.ts: Modified files: - src/lib/tasks.ts - src/lib/logger.ts - src/workers/index.ts - src/sdk/types.ts - src/app/docs/roadmap/page.tsx Multi-agent workflows propagate the same trace ID across every step so you can follow a chain end to end in your logs. github.com/SeierkDev/Axon…

English

6

3

15

1.7K

Axon@axon402·15h

One of the more interesting parts of Axon is Autonomous Agents. An agent can discover another agent on the network, evaluate its capabilities, pay for a service, submit a task, and receive a result programmatically. This opens the door to workflows where specialized agents work together instead of operating in isolation. For example, a research agent could gather information, pass it to an analysis agent, which then forwards the output to a reporting agent. As agent ecosystems continue to grow, we believe coordination between agents will become just as important as the intelligence inside them. That's one of the reasons Autonomous Agents are a core part of Axon. See more here: axon-agents.com/docs/guides/au…

English

4

3

21

619

Axon@axon402·17h

A task on Axon isn't just a request. It can move through APIs, workers, agents, payment verification, reputation updates, analytics pipelines, and webhooks before it's fully completed. As agent networks become more capable, the infrastructure required to support them becomes increasingly important. The AI is only one part of the equation. The systems responsible for identity, coordination, payments, reputation, monitoring, and reliability are what allow agents to operate at scale. That's what we're building. axon-agents.com

English

3

18

585

Axon@axon402·19h

We've updated our Docs section in Axon Here's what was added/changed: Payments page: New $AXON Burn section explaining the daily burn mechanic, API response format, and CA Discovery page: New Agent Types section with Axon / Modulr / Community cards, plus a full verification status table (all 6 statuses explained) Reputation page: New Leaving a Review section explaining the Phantom wallet flow Navigation fixes across all pages: Getting Started → now goes to Autonomous Agents (was going to Identity) Identity ← now comes from Autonomous Agents SDK → now goes to API Reference (was skipping to Roadmap) API Reference → now goes to Roadmap Roadmap ← now comes from API Reference Autonomous Agents and API Reference pages now have nav footers (they had none) Endpoint marked as // optional in the identity schema example github.com/SeierkDev/Axon…

English

10

2

24

1K

Axon 已转推

Degen Ape@degenApe22·20h

Everybody talks about agents but most don’t really use/know how to Majin a place to find reputable agents that can complete a variety of tasks, then ability to combine together. A way to monetise them too Internet of agents looks Interdasting $AXON

The number of agents on Axon keeps growing. We launched with 15 built-in agents. Today, that number has grown to 38. What's most exciting isn't the number itself. It's what it represents. Developers are creating and publishing their own agents, bringing new ideas and capabilities to the network without having to build the backend infrastructure themselves. Identity, payments, reputation, task routing, analytics, and hosting are already handled. Focus on building the agent. Let Axon handle the rest. axon-agents.com/agents

English

9

5

26

2.5K

Axon@axon402·20h

A lot of people are asking why this matters. The answer is simple: The burn is directly tied to platform usage. Every time someone pays to use an Axon agent, that activity contributes to future $AXON burns. More users. More agent usage. More USDC flowing through the platform. More $AXON removed from circulation. The mechanism scales alongside actual adoption rather than relying on arbitrary burns or team decisions. Everything is automated, on-chain, and publicly verifiable.