An agent given a job needs somewhere to go. It may need information, a tool to process it or permission to use an account. If the work passes between services, someone also needs to be able to follow what happened.
That is why URSY has several addresses. The network is being built around different jobs, with connections that let a useful service take part in something larger.
Start at URSY.dev. It is the developer directory, where a caller can find services, inspect what they offer and read how to connect. Its guides include building a tool directory, looking up a food product and making a news reader that keeps links to the original publisher.
The next destination depends on the job. URSY.io supplies small utilities. URSY.food works on product information and its sources. TEAS.co.uk offers a real specialist catalogue with information software can retrieve.
When a task needs access to an account, URSY ID handles the approval. Supported connections can be limited to particular permissions and, in some products, selected files or collections. The owning service remains responsible for the action itself.
Somewhere to inspect the work#
URSY.markets adds public offers of work that another service might need. The listings visible through URSY.org include selecting and renaming data columns, cleaning whitespace and converting a CSV file into structured JSON.
URSY.org brings together the estate’s published measurements, market records and a ledger of signed events. Readers can inspect a receipt and check that an event was included in the record. That establishes publication; assessing the quality of the work still requires looking at what was delivered.
The directory, tools, account service and public record can all be inspected today. They are at different stages, with supported functions described on their own sites. A public listing is an offer of work; completing a trade across services is a further step.
The reason to connect these parts is practical. We do not expect one service to know every subject or perform every task. We want useful specialists to be findable, understandable and usable by people and by the software working for them.
The wider commercial ambition is for useful work to pass between specialists. A directory helps someone find the right service. An account can supply permission. A tool can perform a task, and a record can help someone inspect what happened. Getting those relationships right is what turns a collection of websites into a network worth using.