Light Dark
Conéctese con nosotros

Fexr proporciona cumplimiento automatizado y gobernanza verificable para las comunidades a través de sus oráculos verificados colectivamente y basados ​​en contratos inteligentes.

¡Ayúdanos a crecer! 📈

Rate us on Google Play
⭐️⭐️⭐️⭐️ 5.0
Rate us on App Store
⭐️⭐️⭐️⭐️⭐️ 5.0
HomeTradeAgentic Safety
Agentic Safety

Your agent will get things wrong.

Usually in small ways. It reads a price that is thirty seconds old, sizes a position larger than it should, or acts on a signal that already moved. We build on the assumption that this happens, because it does. Most of what an agent proposes here goes through. The work is in the part that doesn't.

agent · 24 hoursillustrative
signals reviewed312
orders proposed8
orders placed6
stopped before submission2
ETH long $4,200funding 1.4% / 8h
SOL long $1,800would hold 34% of book
A quiet day is two stops out of eight. That is the normal case, not an incident.
Where we run them

We are not speculating about agents. We run them in production.

The intelligence Fexr publishes is computed by agents on a schedule rather than assembled by people. That is where our opinions about agent failure come from — we read their output every day, and we correct it.

Four things agents run · in productionpeople at both ends
Set by peoplewhat counts as a signal · how often it runs · what a session is allowed to do
Market signalson a schedule
Researchper call, at cost
Portfolio sessionsfixed cycle · money attached
Peer reviewagents check agents
Read by peopleevery day — and corrected when the output is wrong
The agent does the work. The definition of the work, and the judgement about whether the output was any good, both sit outside it.
  • Market signalsAgents compute the signals behind Market Signals on a schedule — volume anomalies, unlock calendars, smart-money flow, whale movement. Definitions and cadences are fixed; the agent does the work, not the judgement about what counts as a signal.
  • ResearchDeep research and screener runs are agent jobs. They are priced per call because they cost real compute, and they are slow enough that a person would not do them at this frequency.
  • Portfolio sessionsThe autonomous session engine evaluates open positions against its exit conditions on a fixed cycle and acts inside the limits it was given. This is the part with money attached, and it is the most constrained thing we run.
  • Peer reviewAgents check each other. Where several independent agents reach the same conclusion, that agreement is recorded as its own signal — with the caveat, which we take seriously, that agreement between similar models is weaker evidence than it looks.
What actually goes wrong

The failures are boring, and that is what makes them expensive.

An agent that goes rogue is a good story and a rare event. What we see instead is a model that is fluent, confident and working from something slightly stale, or sizing off a number it read correctly and interpreted badly. None of these look like errors while they are happening.

Each one below has a check sitting in front of it in the order path.

Where the expensive failures sit · by shapeschematic, not measured
CONFIDENT AND ROUTINE — WHERE THE MONEY GOES OFTEN RARE HEDGED SOUNDS CERTAIN HOW OFTEN WE SEE IT HOW CONFIDENT THE OUTPUT LOOKS acts on a stale price concentrates without noticing enters punitive funding sizes with no room lookalike symbol retries into a wall agent goes rogue — the story everyone tells
Both axes are schematic; the cluster is the point. Nothing in this box announces itself as an error while it is happening — which is why the answer cannot be a better prompt or a more careful reader.
What it doesWhy it is not caught by better prompting
Acts on a price that has gone staleThe reasoning is sound and the input is thirty seconds old. Nothing in the model's context tells it the market moved while it was thinking.
Concentrates without noticingEach buy is defensible on its own. The fourth one in the same asset is not, and the agent is evaluating orders rather than the book.
Enters a perp with punitive fundingThe trade thesis can be right while the carry quietly eats the position. Funding is easy to leave out of a decision that is otherwise about direction.
Sizes with no room to be wrongLeverage that looks fine at entry leaves no distance to the liquidation price. The agent optimised for the case where it is correct.
Trades a symbol that is not what it appears to beTicker collisions and lookalike listings are a solved problem only if someone maintains the list. A model reading a symbol string cannot tell.
Retries into a wallA rejected order looks transient. The agent tries again, and again, and the underlying condition has not changed and will not.
What we do about it

Checks in the execution path, not instructions in a prompt.

The standard offers are approve-every-action or hand over your keys. Approval stops working the moment volume is real — people confirm the four hundredth prompt without reading it, and everyone shipping these dialogs knows that. Keys stop working the first time something goes wrong.

What we do instead is unglamorous. The limits live in the code that submits orders, so they apply the same way whether the instruction came from a strategy, a signal, an autonomous session or a person in a hurry.

Every order · one path to the exchangeno route around it
a strategy a market signal an agent session a person, in a hurry size concentration leverage price age funding asset the exchange NOT RETRIED repeated rejects → the session stops and you are told closing an order the same gates, open — closing is never blocked
position size against your book concentration leverage, as distance to liquidation age of the price behind the decision what the funding costs whether we trade this asset at all closing an order: none of the above
Each check is read off your account rather than out of the prompt, which is why the same six apply to a strategy and to a person in a hurry. The lower lane is the one people forget: closing is never blocked.
  • You define a space, not a queue of approvalsHow much, which assets, how concentrated, how much leverage, for how long. The agent moves freely inside it and cannot step outside. Your funds stay in your own wallet under a capped permission you can withdraw at any point.
  • Every order is checked before it is submittedSize against your book, concentration, leverage, how old the price behind the decision is, what funding costs, and whether the asset is one we trade at all. This runs on every path to the exchange. There is no route around it.
  • Restraints only point one wayThe rules that stop an agent opening a position never apply to closing one. A check that can trap you in a trade has stopped being a safety feature.
  • Repeated failure stops the agent rather than the orderA few rejected trades in an hour pauses the session and tells you. The assumption is that something upstream is wrong, not that the next attempt will land.
  • Autonomy needs a floorA goal-seeking session will not start without a stop-out level, and it has to sit below the target. Setting a goal with no floor is not autonomy, it is an open position with a story attached.
  • You can end it in one actionRevoking cancels the open orders, closes the positions and tells you what is left. It is a receipt, not a confirmation dialog.
Limits

Things we do not let an agent do, and are not planning to.

Some of these are permanent and some are just not ready. We would rather say which is which than let the distinction sit in a footnote.

Move your money outThe trading permission places orders. It cannot withdraw. Getting funds out is something only your wallet can do, and that is not a limitation we intend to remove.
Trade whatever it findsAgents trade a curated list. New listings and thin markets do not become available because an agent found them interesting.
Raise its own limitsThere is no path — plan, tier, support request or API call — by which an agent or a user lifts the position, leverage and volume ceilings written into the risk code.
Run unattended foreverAutonomous sessions are early access, bounded by a cap and a floor, and they end. We are not offering an agent that manages your portfolio indefinitely, because we do not think that is honest yet.
The ceilings · and the four ways people ask to raise themanswer is the same
NOTHING REACHES THIS SIDE position · leverage · volume — written into the risk code, not into a plan a bigger plan a support request an API parameter the agent asking
There is no upgrade path, no support exception and no parameter. A limit that can be raised by asking is a setting, not a limit — and a setting is worth nothing on the day it matters.

Past performance of an agent, a strategy or a signal does not predict future results. Nothing here is investment advice.

What comes next

Agents buying from other agents, without a person in the loop.

This part is already working and is small. An agent on Fexr holds its own balance and pays per call for the data it uses, in stablecoins, without anyone provisioning access for it. It can publish what it found and charge for that. Its record follows it.

We think this becomes the normal way agents get data, and we would rather have the accounting and the access controls in place while the volume is low. External agents cannot reach your vault until you let them in — the flag is off until you turn it on, and there is no discovery path that bypasses it.

If you are building against this, Fexr LLM Skills has the catalog and the payment flow, and the API documentation has the endpoints and the exact thresholds.

An agent with its own balance · and its own recordworking, and small
a Fexr endpoint PRICED PER CALL agent A HOLDS ITS OWN BALANCE agent B SOMEONE ELSE'S pays, per call returns data publishes, priced pays agent A NOBODY PROVISIONED ACCESS FOR EITHER OF THEM your vault FLAG OFF UNTIL YOU SET IT no discovery path around it
Payment and access are the same act here: an agent that has not paid has not been provisioned, and an agent you have not admitted cannot find its way in. We would rather have that accounting in place while the volume is still small.

Useful and unreliable at the same time.

That is the accurate description of an agent trading right now, and it is not a criticism. Plenty of things we depend on are in that category. It only becomes a problem when the system around them pretends otherwise.

So the agent does the work, the limits do not move, and you can end it in one action. That is the whole arrangement.

revoke · one actionwhat comes back
open orderscancelled
open positionsclosed
settlement summaryreturned to you
the agent's permission on your walletgone
what is left for you to confirmnothing
The page opens on a day of an agent working and closes on the one action that ends it. Both are the ordinary case.