Nexus Tools ouvre ses données aux assistants IA par un serveur MCP (Model Context Protocol). Un assistant connecté peut chercher dans le catalogue, guider un joueur avec le NPS, consulter la marketplace et, si vous l'y autorisez, gérer votre inventaire, vos commandes et vos contributions.
Adresse du serveur :
https://tools.services.nexus/mcpTransport HTTP « Streamable HTTP », sans session. Le serveur suit la spécification MCP 2026-07-28 et répond aussi aux clients de 2025.
Claude (web, bureau, mobile) : Paramètres → Connecteurs → Ajouter un connecteur personnalisé, puis collez l'adresse du serveur.
ChatGPT : Paramètres → Applications et connecteurs → mode développeur, puis créez un connecteur avec l'adresse du serveur.
VS Code (GitHub Copilot) : ajoutez le serveur dans .vscode/mcp.json.
{
"servers": {
"nexus-tools": {
"type": "http",
"url": "https://tools.services.nexus/mcp"
}
}
}Cursor : ajoutez le serveur dans ~/.cursor/mcp.json.
{
"mcpServers": {
"nexus-tools": {
"url": "https://tools.services.nexus/mcp"
}
}
}Un client qui ne parle que stdio passe par mcp-remote :
npx -y mcp-remote https://tools.services.nexus/mcpLa première fois qu'un outil personnel est appelé, l'assistant ouvre la connexion à votre compte Nexus Tools.
Les outils publics (catalogue, lieux, NPS, marketplace en lecture) répondent sans connexion. Les outils personnels demandent votre accord, par la connexion OAuth du site, pour ces accès :
openid — vous identifierprofile — lire votre nomemail — lire votre adresse e-mailoffline_access — rester connectée sans vous redemanderinventory:read — lire votre inventaireinventory:write — ajouter, déplacer et modifier les lots de votre inventairerefining:read — lire vos ordres de raffinagerefining:write — lancer, modifier et retirer vos ordres de raffinage, et collecter leurs matériaux dans votre inventairemarkers:read — lire vos marqueurs de positionmarkers:write — créer, modifier et supprimer vos marqueurs de positionplayers:read — voir vos amis, vos organisations et leurs membres, leur présence et leur position en jeu, et les invitations reçuesplayers:write — ajouter et retirer des amis, et partager vos lieux privés, évènements et collections de marqueurs avec d'autres joueursevents:read — lire vos évènements, vos inscriptions et votre présence prévueevents:write — créer et modifier vos évènements, vous y inscrire ou vous désinscrire, et prévoir vos sessions de jeucrafting:read — lire les blueprints que vous possédezcrafting:write — marquer des blueprints comme acquis ou les retirerreputation:read — lire vos réputations auprès des factionsreputation:write — modifier vos réputations auprès des factionsnotes:read — lire votre bloc-notesnotes:write — écrire dans votre bloc-notesmarketplace:read — lire votre panier, vos commandes et vos magasinsmarketplace:write — remplir votre panier, passer et suivre vos commandes, mettre en vente et gérer les commandes de vos magasinscontributions:write — proposer des contributions en votre nom (lieux, plans, objets)Chaque modification (inventaire, panier, commande, mise en vente, contribution) vous est montrée avant d'avoir lieu, et n'a lieu que si vous la confirmez.
Vous retirez l'accès d'un assistant à tout moment dans vos paramètres, rubrique « Applications connectées ».
Ouvrir mes paramètresLes assistants compatibles MCP Apps affichent certains résultats sous forme de vues : annonces de la marketplace avec un bouton « Ajouter au panier », fiches d'objets et de lieux, inventaire, plans, boussole du NPS. Les autres reçoivent le même contenu en texte.
115 outils, décrits ici comme l'assistant les lit (en anglais).
searchSearch everything on Nexus ToolsSearch every public collection of Nexus Tools at once (blueprints, items, places, missions, factions, marketplace listings, shops, organizations, cargo ships) and return the best matches with their type, id/slug and link. Use it first when you do not know what kind of thing the user means, then call the dedicated tool (get_item, get_place, get_listing, ...).
search_blueprintsSearch for a blueprintSearch for up to 3 crafting blueprints with a generic query (fuzzy on the name) and return their slugs and full names to use with other tools.
get_blueprint_by_slugGet blueprint details by slugRetrieve detailed information about a blueprint, recipe, obtention, statistics, ... using its slug.
search_itemsSearch the item catalogSearch the Nexus item catalog (ship components, weapons, armor, vehicles, resources...) with optional filters, sorted by name. Call list_item_facets to know the exact category and manufacturer values.
list_item_facetsList item categories and manufacturersList the categories, subcategories and manufacturers present in the item catalog, to build exact filters for search_items.
get_itemGet an itemvueFull sheet of a catalog item by slug: description, statistics, where to get it, blueprints that craft it or consume it, variants, set, and vehicle/weapon/resource specifics (resource market prices included).
compare_itemsCompare itemsCompare up to 5 items of the same kind side by side, statistic by statistic. Items of another kind than the first are rejected.
get_missionGet a missionGet a Star Citizen mission (contract) by its id, as returned by search or search_missions: type, category, faction, description (it holds the objectives), aUEC reward, legality, whether it can be shared, the blueprints it rewards, where it is played and the community tip. When the user is signed in with crafting access, each blueprint says whether they own it.
search_missionsSearch missionsSearch the missions still offered in game, as the /missions page filters them: by words of the title or description, by faction (id from search, list_factions or get_mission, or the faction's name) and/or only missions that reward blueprints. Sorted by title, paginated. Mission ids work with get_mission.
list_factionsList factionsList Star Citizen factions: the reputation factions of the /reps page with their careers and the names of each career's ranks, and the mission factions of /missions/factions with their number of missions and blueprints (both kinds are matched by name). Optionally filter by words of a faction, career or rank name. Use get_faction for the full rank ladders and the faction's missions.
get_factionGet a factionGet a Star Citizen faction by name (or mission faction id from search, list_factions or get_mission): its description, standings, careers with every rank (relative level, reputation needed), and its missions still offered in game with the blueprints they reward.
search_placesSearch placesSearch the places of the Star Citizen universe known to Nexus (systems' planets and moons, cities, stations, outposts, spaceports, districts, buildings, shops), with filters on type, system, celestial body, service or parent place. When the user is signed in, the first page also lists their private places (visible only to them or their organization) that match.
list_place_facetsList place types, systems and bodiesList the place types, star systems, celestial bodies and services known to Nexus, with their slugs, to build filters for search_places.
get_placeGet a placevueFull sheet of a place by slug: description, tip, services, parent chain, child places, shops below it, missions given there, NPS coordinates when known, its lore (starmap description and Galactapedia article, in English) and the list of its maps (use get_place_plan for a map's content). Also opens the signed-in user's private places (slug starting with prive-).
get_place_planGet a place mapvueContent of one map of a place. A drawn map returns its full geometry: extent in centimetres, levels with rooms, walls, doors, labels, measures, and markers (as fractions of the extent). An image map returns its image URL and markers. Without planId, the first map of the place.
nps_locateLocate a /showlocation reading (NPS)vueNexus Positioning System. Give the line the game copies to the clipboard after the /showlocation chat command ("Coordinates: x:… y:… z:…", in metres, star system frame). Returns the celestial body the player is on or near, latitude/longitude/altitude, the nearest places with recorded coordinates (including the signed-in user’s private places), and, when a destination slug is given, the distance and the compass heading to follow. Coordinates of different systems do not compare: pass system when the player is in deep space.
search_loreSearch the Star Citizen loreSearch the Galactapedia, RSI's official encyclopedia of the Star Citizen universe (history, people, companies, species, systems, planets, ships, events, culture), and return the most relevant articles with an excerpt. Words are matched in English: translate the player's question first (e.g. « guerre contre les Vanduul » → "Vanduul war"). Then call get_lore_article for the full text. Call it without query to list the categories.
get_lore_articleRead a Galactapedia articleFull text of a Galactapedia article (Markdown, English) by id or slug, with its categories, tags, the articles it links to, and the starmap systems or bodies it describes. Use it to answer lore questions accurately instead of relying on memory.
get_star_systemGet a star system from the starmapLore sheet of a star system from RSI's starmap: description, affiliation (UEE, Banu, Xi'an, Unclaimed…), population, economy and danger ratings (0-10), jump points to other systems, and its stars, planets, moons, stations and belts with their own descriptions. Call it without system to list every system. For in-game coordinates and services, use get_place instead.
search_listingsSearch the marketplacevueSearch the player marketplace of Nexus: listings of player shops with price (aUEC), available stock, hand-over place and shop. Only listings in stock unless includeSoldOut. Call list_listing_facets for exact categories and systems.
list_listing_facetsList marketplace categories and systemsList the categories, hand-over systems and sizes of the marketplace listings in stock, to build filters for search_listings.
get_listingGet a marketplace listingvueOne marketplace listing by id: description, price, available stock, hand-over place, catalog item and shop.
get_shopGet a player shopvueA player shop by id: description, owner, number of delivered orders, and its listings on sale (paginated).
list_missingList what's missing in the catalogThe catalog gaps players run into most (the site's “What's missing” page), most visited pages first over 30 days: placeImage (places without an image), placePlan (stations, spaceports, outposts and buildings without a map), itemSection (vehicles, weapons, resources without their figures), stalePrices (resource prices not confirmed for two weeks), missionPlace (missions without a location). Each entry has its page, where to fill it and the points it earns, to suggest contributions to the user.
get_leaderboardContributor leaderboardThe community contributor leaderboard (the site's /classement page): players or public organizations (sum of their members' points), for the current month (default) or all time, top 50. Players who chose to hide are left out. When the user is signed in with the profile scope, `me` gives their own rank and points.
whoamiConnected Nexus accountAccès : profileReturn the Nexus Tools account the assistant acts for, and the access it was granted. Calling it without being signed in starts the sign-in.
list_my_blueprintsList my blueprintsAccès : crafting:readList the crafting blueprints the signed-in player owns (those they marked as acquired, plus the default blueprints everyone owns), sorted by name, optionally filtered by part of the name, category and subcategory. Slugs work with get_blueprint_by_slug and set_blueprint_owned.
set_blueprint_ownedMark a blueprint as ownedmodifieAccès : crafting:writeMark a crafting blueprint as acquired by the signed-in player (owned: true, the default) or remove it from their blueprints (owned: false), like the button on the blueprint page. Default blueprints are owned by everyone and cannot be removed. Asks the user to confirm first.
blueprint_owners_in_orgWho in my organizations owns a blueprintAccès : crafting:readList the members of the signed-in player's organizations who own a crafting blueprint, as the blueprint page shows them: one organization if given, otherwise each of the player's organizations. Default blueprints, owned by everyone, list only members who marked them.
my_reputationsMy faction reputationsAccès : reputation:readList the signed-in player's reputations as the /reps page shows them: for each faction, the standing (when it has one) and the current rank of each career, with whether the faction is started or maxed. Filter by words of a faction, career or rank name, or keep only started factions.
update_reputationUpdate a faction reputationmodifieAccès : reputation:writeChange the signed-in player's reputation with a faction, as on the /reps page: its standing, and/or the current rank of one career (career may be left out when the faction has a single career). Names come from list_factions, get_faction or my_reputations. Asks the user to confirm first.
create_private_placeCreate a private placemodifieAccès : inventory:writeCreate a private place (a base, hangar, hideout… missing from the public catalog) inside a public place, visible only to the signed-in player or also to one of their organizations. It becomes an inventory location where lots can be stored. At most 200 per account. Asks the user to confirm first.
update_private_placeChange a private placemodifieAccès : inventory:writeChange a private place the signed-in player created (slug starting with prive-, from search_places): name, type, parent, description, NPS position or the organization that sees it. Only the given fields change; null clears description, position or organization. Only its creator can change it. Asks the user to confirm first.
delete_private_placeDelete a private placemodifieAccès : inventory:writeDelete a private place the signed-in player created. Nothing stored there is lost: its inventory location becomes a personal location of the same name, and lots other players stored there move to a personal location of theirs. Only its creator can delete it. Asks the user to confirm first.
propose_private_placePropose a private place to the public catalogmodifieAccès : contributions:writePropose a private place the signed-in player created to the public catalog, as the site's Propose button does: a new-place contribution, reviewed by the community (published at once for contributor level 3 or more). The place stays private during review; once published it becomes the public place and the lots stored there stay. The description is left out unless withDescription is set (it often holds organization notes). Asks the user to confirm first.
cart_viewView my cartvueAccès : marketplace:readThe signed-in player's marketplace cart, grouped by shop as it would be ordered now (one order per shop), with any line that cannot be ordered anymore.
cart_addAdd to my cartmodifieAccès : marketplace:writeAdd a quantity of a marketplace listing (id from search_marketplace) to the signed-in player's cart. Nothing is ordered or reserved until cart_checkout. Asks the user to confirm first.
cart_updateChange my cartmodifieAccès : marketplace:writeSet the quantity of a cart line, or remove it with quantity 0. Asks the user to confirm first.
cart_checkoutCheck out my cartmodifieAccès : marketplace:writeOrder the whole cart: one order per shop, all or none, at the prices shown by cart_view. Each shop then confirms (which reserves the stock), prepares and hands over. For a shop without a handover place, or to meet elsewhere, give proposedPickup. Asks the user to confirm first.
order_nowBuy a listing nowmodifieAccès : marketplace:writeOrder a quantity of one listing straight away, without the cart. The shop then confirms (which reserves the stock), prepares and hands over. Asks the user to confirm first.
request_custom_orderAsk a shop for a quotemodifieAccès : marketplace:writeSend a shop a free-form request (something it does not list, a service, a large quantity). The shop answers with a quote the player then accepts or declines with order_action. Asks the user to confirm first.
my_ordersMy ordersAccès : marketplace:readThe signed-in player's marketplace orders as a buyer, newest first, with what they can do on each now (order_action).
get_orderRead an orderAccès : marketplace:readOne order the player bought or one their shop received: lines, handover, total, its messages and quotes, and the actions open to them now.
order_actionMove an order alongmodifieAccès : marketplace:writeAct on an order. Buyer: accept or decline a quote, cancel. Seller: confirm a direct order (reserves the stock), quote a price, refuse, mark ready, deliver (the stock and any linked inventory lot go down). get_order and my_orders list what is possible now. Asks the user to confirm first.
order_messageWrite on an ordermodifieAccès : marketplace:writePost a message in an order's thread, to the shop or to the buyer. Asks the user to confirm first.
my_shopsMy shopsAccès : marketplace:readThe shops the signed-in player sells in (default shop first), with how many orders wait for them.
shop_ordersOrders of my shopAccès : marketplace:readThe orders a shop the player sells in received: in progress (oldest first, default) or closed (newest first).
shop_listingsListings of my shopAccès : marketplace:readThe listings of a shop the player sells in, as the back office shows them: on sale (active), sold out, or withdrawn (hidden).
sell_lotSell an inventory lotmodifieAccès : marketplace:writePut one of the player's inventory lots (id from list_inventory) on sale in a shop they sell in (my_shops; the default shop when omitted). The listing follows the lot: its stock and handover place come from it, optionally capped with limit. Asks the user to confirm first.
update_listingChange a listing of my shopmodifieAccès : marketplace:writeChange a listing of a shop the player sells in: adjust its stock (listings that do not follow a lot), change the cap of a lot-linked listing, its price, or withdraw it from sale and put it back. Asks the user to confirm first.
list_inventoryList my inventoryvueAccès : inventory:readList the signed-in player's inventory lots (item, quantity, quality, location, what parcels reserve and which shops sell it), most recently changed first. Lot ids are what the other inventory tools take.
search_inventory_locationsFind an inventory locationAccès : inventory:readFind where lots can be stored: the game's places (stations, cities, outposts) and the locations the player named themselves. Returns ids for add_inventory and move_inventory_lot.
add_inventoryAdd to my inventorymodifieAccès : inventory:writeAdd lots to the signed-in player's inventory at one location. A lot matching one already held there (same name, quality, unit and note) tops it up instead of creating a second one. Asks the user to confirm first.
move_inventory_lotMove a lotmodifieAccès : inventory:writeMove one of the signed-in player's lots to another location, whole or in part (moving part of it splits the lot). Asks the user to confirm first.
update_inventory_lotChange or remove a lotmodifieAccès : inventory:writeChange one of the signed-in player's lots: set or adjust its quantity, its quality, unit, name or note, its sharing with the organization, or remove it. Asks the user to confirm first.
create_parcelSend a parcel to a playermodifieAccès : inventory:writeSeal a parcel from the signed-in player's inventory lots (ids from list_inventory) and get the 8-character code to give to the recipient, who accepts it with accept_parcel or on the site. The quantities stay in the inventory, reserved, until the parcel is accepted (they then leave it), cancelled, or the code expires after 24 hours. Asks the user to confirm first.
list_parcelsList my parcelsAccès : inventory:readList the parcels the signed-in player sent or received over the last 30 days, newest first: code, state (pending, delivered, cancelled, expired), contents, the other player and where it was stored. Codes are what cancel_parcel takes.
accept_parcelAccept a parcelmodifieAccès : inventory:writeAccept a parcel another player sent, by its code: shows what it holds and who sent it, then moves its lots from the sender's inventory into the signed-in player's, at the location given (a matching lot there is topped up). Wrong codes count against the player (ten in ten minutes, then a wait). Asks the user to confirm first; declining leaves the parcel waiting.
cancel_parcelCancel a parcelmodifieAccès : inventory:writeTake back a parcel the signed-in player sent that is still waiting (code from list_parcels): its code stops working and the reserved quantities are free again. Nothing had left the inventory. Asks the user to confirm first.
list_refining_jobsList my refining ordersAccès : refining:readList the signed-in player's refining orders (refinery, method, materials with quality and cSCU yield, cost, time left), finished ones first. Order ids are what the other refining tools take.
start_refining_jobTrack a refining ordermodifieAccès : refining:writeStart tracking a refining order the player just launched at a refinery terminal: refinery, method, the materials it will yield (quality, cSCU) and the processing time. The countdown starts now. Asks the user to confirm first.
update_refining_jobChange a refining ordermodifieAccès : refining:writeChange one of the signed-in player's refining orders: its refinery, method, materials, processing time (counted from the original start), cost or note. Only the given fields change; lines replace all the order's lines. Asks the user to confirm first.
collect_refining_jobCollect a refining ordermodifieAccès : refining:writeCollect a finished refining order: its materials become lots of the player's inventory (at the refinery unless another location is given; a matching lot there is topped up) and the order is removed. Inert materials are left out unless includeInert is set; pass lines when the actual yield differs. Asks the user to confirm first.
delete_refining_jobRemove a refining ordermodifieAccès : refining:writeRemove one of the signed-in player's refining orders without adding anything to the inventory (a cancelled or mistaken order). To store its materials, use collect_refining_job instead. Asks the user to confirm first.
list_markersList my position markersAccès : markers:readList the signed-in player's position markers (spots saved in game to come back to: ore rocks, wrecks, caves…), newest first, with their collection, body, latitude/longitude and note, including markers of collections their organizations share. Marker ids are what the other marker tools take.
add_markerMark a positionmodifieAccès : markers:writeSave a position marker from a /showlocation reading, to come back to it later (the Nexus App NPS can guide there): for example ore rocks found without a mining laser. On a planet or moon the marker follows its rotation. Asks the user to confirm first.
update_markerChange a position markermodifieAccès : markers:writeChange one of the signed-in player's markers: name, category, note, collection, or its position from a new /showlocation reading. Only the given fields change; null removes the note or the collection. Asks the user to confirm first.
delete_markerDelete a position markermodifieAccès : markers:writeDelete one of the signed-in player's markers, for example once the ore is mined. Asks the user to confirm first.
list_marker_collectionsList my marker collectionsAccès : markers:readList the marker collections the signed-in player sees: their own, those an organization of theirs shares, and those another player invited them to, each with its number of markers, color and who it is shared with. Also lists the player's organizations, to share a collection with. Collection ids are what the other collection tools, list_markers and the sharing tools (kind markerCollection) take.
create_marker_collectionCreate a marker collectionmodifieAccès : markers:writeCreate a marker collection (a folder of position markers, with its color on the map), kept to the player or shared with one of their organizations, whose members then see its markers. Markers go into it with add_marker or update_marker. Asks the user to confirm first.
update_marker_collectionChange a marker collectionmodifieAccès : markers:writeRename one of the signed-in player's marker collections, change its color, or who sees it (one of their organizations, or null for the player alone). Only the given fields change. Players invited one by one keep their access (see unshare). Asks the user to confirm first.
delete_marker_collectionDelete a marker collectionmodifieAccès : markers:writeDelete one of the signed-in player's marker collections. Its markers are kept, without a collection; the organization and the players it was shared with no longer see them. Asks the user to confirm first.
list_players_in_gameList friends in game and where they areAccès : players:readList the signed-in player's friends and organization members who are in game right now and share their position with them, with where they are (body, latitude/longitude, or star system space), their activity and when the position was read; the player's own position too if they share it. Positions are system-frame coordinates in space, or body-frame coordinates on a planet or moon, like the NPS.
list_friendsList my friendsAccès : players:readList all the signed-in player's friends, in game or not, like the Friends card of their profile: who is playing now (with the activity they declared and since when), who planned their next session (when, for what), and the organization shown with their name. Friends playing come first, then planned sessions, then the others by name. Friend ids are what remove_friend takes. For where friends are in game, use list_players_in_game.
my_friend_codeShow my friend codeAccès : players:readShow the signed-in player's pending friend code, to hand to someone who then enters it (add_friend, or the Friends card of their profile) so both become friends. A code works once; when the player has none (never asked for, or already used), says where to generate one on the site.
add_friendAdd a friend by codemodifieAccès : players:writeBecome friends with the player who gave the user their friend code (8 characters, like "K7QD-92PX"; case and dash optional). Both appear in each other's friend list and the code is used up. Asks the user to confirm first.
remove_friendRemove a friendmodifieAccès : players:writeEnd a friendship of the signed-in player, on both sides: the user also disappears from the other's list. The friend is named by id (from list_friends) or exact name. Asks the user to confirm first.
list_my_orgsList my organizationsAccès : players:readList the organizations the signed-in player is a member of, by name: tag, description, whether it is public, the player's rank and whether they can edit it, member count, and the one shown next to their name. Organization ids are what get_org and org_inventory take.
get_orgShow one of my organizationsAccès : players:readShow one organization the signed-in player is a member of, like its page: name, tag, description, visibility, the player's rank, and its members with their rank, who is playing now (activity, since when) and who planned a session (when, for what, and the organization event if any). Members playing come first, then planned sessions, then the others by name.
org_inventorySearch an organization's shared inventoryAccès : inventory:readList the inventory lots that members of one of the signed-in player's organizations share with it, like the organization's inventory page: item, quantity, quality, location and which member holds it, grouped by location. Filter by part of the item name, location, minimum quality or member.
list_my_eventsList my eventsAccès : events:readList the upcoming events the signed-in player sees on Nexus Tools: those of their organizations, their personal events, the ones other players invited them to, and those they registered to, soonest first, with their registration status. Set includePublic to add other organizations' public events (the community calendar). Covers from a day ago to three months ahead. Also gives the player's in-game status and planned session. Event ids are what the other event tools take.
get_eventRead an eventAccès : events:readRead an event the signed-in player can see (organization or personal event): description, dates, meeting point, roles with how many registered and wanted, registration questions, the registered players (with their answers when the player manages the event), the linked squad and the player's own registration. Event ids come from list_my_events.
register_eventRegister to an eventmodifieAccès : events:writeRegister the signed-in player to an event they can see (member of its organization, or invited), or change their registration (role, answers); a withdrawn registration comes back. Pass the role (required when the event offers roles) and answers to its questions, as get_event lists them; on a change, what is not given is kept. Asks the user to confirm first.
withdraw_eventWithdraw from an eventmodifieAccès : events:writeWithdraw the signed-in player's registration from an upcoming event. Their answers are kept but no longer counted; register_event brings the registration back. Asks the user to confirm first.
create_eventPlan an eventmodifieAccès : events:writePlan an event: in one of the signed-in player's organizations (any member can), or a personal event outside any organization when organization is omitted (always private; up to 50 upcoming). Give the start and either the end or the duration (at most 48 h), and optionally a meeting point, the roles players pick when registering and questions they answer. Asks the user to confirm first.
update_eventChange an eventmodifieAccès : events:writeChange an event the signed-in player manages (their own, or any of their organization's when they are one of its editors). Only the given fields change; moving the start without an end keeps the duration. roles and questions replace the whole list: pass back the ids from get_event to keep the registrations and answers tied to them. Asks the user to confirm first.
delete_eventDelete an eventmodifieAccès : events:writeDelete an event the signed-in player manages (their own, or any of their organization's when they are one of its editors), with its registrations and shares. Cannot be undone. Asks the user to confirm first.
plan_sessionPlan my next sessionmodifieAccès : events:writePlan the signed-in player's next game session, shown to their friends and organization members: a time (within 14 days) and an activity, or an upcoming event they are registered to (its start and title by default). Replaces the session already planned; starting to play uses it up. Asks the user to confirm first.
cancel_planned_sessionCancel my planned sessionmodifieAccès : events:writeCancel the signed-in player's planned next session, so their friends and organization members no longer see it. Asks the user to confirm first.
set_playingSet my in-game statusmodifieAccès : events:writeDeclare that the signed-in player is in game, with what they are doing, or that they stopped, as on their profile; friends and organization members see it. The declaration lapses after 4 h unless renewed (calling again renews it). Starting a session uses up the planned one and takes its activity when none is given. Stopping also clears the position they shared. Asks the user to confirm first.
list_sharesSee who something is shared withAccès : players:readShow who one of the signed-in player's events, private places or marker collections is shared with: the players invited one by one or come through the share link, the organization whose members already see it, and the event's share link. Only for what the player manages. Player ids are what unshare takes.
share_with_playerShare with a playermodifieAccès : players:writeInvite a player on one of the signed-in player's events, private places or marker collections: they see it at once and get a notification. The player is found by the start of their name, friends first, as in the site's Share panel. Only for what the player manages. Asks the user to confirm first.
unshareStop sharing with a playermodifieAccès : players:writeTake a player's access away from one of the signed-in player's events, private places or marker collections, whether they were invited or came through the share link. Only for what the player manages; the players come from list_shares. Asks the user to confirm first.
list_invitationsList what was shared with meAccès : players:readList the invitations the signed-in player received, newest first (the site's bell): events, private places and marker collections another player shared with them, with who invited them and a link to open each. Does not mark them seen. kind and targetId are what leave_share takes.
leave_shareStop seeing something shared with memodifieAccès : players:writeGive up an event, private place or marker collection another player shared with the signed-in player (by invitation or through a share link): they no longer see it. A registration to an event stays. kind and targetId come from list_invitations or list_marker_collections. Asks the user to confirm first.
create_share_linkCreate an event share linkmodifieAccès : players:writeCreate the share link of one of the events the signed-in player manages: anyone who has the link can open the event, even without an account. If the event already had one, the old link stops working and those who came through it lose access unless they registered. Events only. Asks the user to confirm first.
revoke_share_linkDisable an event share linkmodifieAccès : players:writeDisable the share link of one of the events the signed-in player manages: the link stops working, and those who came through it lose access unless they registered. Players invited one by one keep it. Events only. Asks the user to confirm first.
get_notesRead my notesAccès : notes:readRead the signed-in player's scratch pad (one free-text note per account, the one of the site's Notes page and side panel), with when it was last saved. It holds at most 20000 characters.
update_notesWrite in my notesmodifieAccès : notes:writeWrite in the signed-in player's scratch pad. mode "append" (default) adds the text at the end, on a new line; "replace" replaces the whole note (an empty text clears it). The note holds at most 20000 characters. Asks the user to confirm first.
my_contributor_standingMy contributor standingAccès : profileThe signed-in player's community contributor standing (points, level, acceptance rate, what is awaiting review) and their latest contributions with their status.
contribute_place_positionContribute a place's NPS positionmodifieAccès : contributions:writePropose the NPS coordinates of a place from a /showlocation reading taken there (in game, standing at the place). The reading is converted to the frame of the body the player is on. Asks the user to confirm first.
contribute_place_editContribute a correction to a placemodifieAccès : contributions:writePropose changes to a place of the catalog (get_place shows the current entry): description, type, services, player tip, shop category and sold items. Only the fields given change. Asks the user to confirm first.
contribute_place_createContribute a new placemodifieAccès : contributions:writePropose a place missing from the catalog, under its parent (a system, planet, moon, city, station…). The slug follows the name. Asks the user to confirm first.
contribute_item_editContribute a correction to an itemmodifieAccès : contributions:writePropose changes to an item of the catalog (get_item shows the current entry). `changes` holds only the fields to change, with the same shape as get_item: description, category, subcategory, manufacturer, size, tier, statistics, obtention, blueprintSlugs, variantGroup, variantName, setId, setName… Renaming needs contributor level 4. Asks the user to confirm first.
contribute_mission_tipContribute to a missionmodifieAccès : contributions:writePropose a player tip for a mission and/or the places where it takes place (mission ids appear in get_place). Asks the user to confirm first.
contribute_item_createContribute a new itemmodifieAccès : contributions:writePropose an item missing from the catalog, as the /items/proposer form does (search_items first: an item whose name gives the same address is refused as a duplicate). The address (slug) follows the name; the image is added later by the team. Optional blocks follow the shape get_item returns: `vehicle` for kind vehicle, `weapon` for kind weapon, `resource` for kind resource (the others are dropped). Goes to community review unless the user is a trusted contributor (level 3 or more). Asks the user to confirm first.
confirm_dataConfirm or flag data that agesmodifieAccès : contributions:writeConfirm, as the site's “Still accurate / No longer accurate” buttons do, data that ages with patches: `sources` = where to obtain a blueprint (slug from search_blueprints), `prices` = the market prices of a resource item (slug from search_items), `services` = the services of a place (slug from search_places). accurate: true dates the data today; false flags it outdated, and the third player to do so opens a report for moderators. Published right away (no review), 1 point within 5 a day, once a week per data and player. Asks the user to confirm first.
list_my_contributionsList my contributionsAccès : profileThe signed-in player's contributions, latest activity first, as on their /contributions page: what they propose (new or corrected places, items, plans, images, missions, confirmations), with the status (in review, published, needs changes with the reviewer's reason and message and the date to fix it before, rejected with the reason, reverted), the points, a link to the entry and, while it is open, the link to edit it on the site.
plan_draft_createStart a place map draftmodifieAccès : contributions:writeStart drawing the map (drawn plan) of a place: an empty draft with one level, or a copy of one of the place's existing drawn plans to correct it. Read the format first: resource nexus://docs/plan-format. Drafts are private to the user and expire after 7 days without changes; nothing is published before plan_draft_submit.
plan_draft_getRead a map draftAccès : contributions:writeRead a draft in full (every level, room, wall, door, label, measure and marker with its id, in cm), or, without draftId, list the user's open drafts.
plan_draft_editEdit a map draftmodifieAccès : contributions:writeApply a batch of operations to a draft, all or nothing: add_level, rename_level, add_room (x/y/w/h, polygon points, or nextTo another room), add_wall (a segment), add_door (snapped to the nearest wall), add_label, add_measure, add_marker (cm, converted), update, move, remove. Coordinates are integer cm from the top-left corner of the extent; north is up. Returns the ids created and the anomalies to check.
plan_draft_replaceReplace a map draftmodifieAccès : contributions:writeReplace the whole draft with a plan document in the drawn plan format (see nexus://docs/plan-format): for agents that prefer writing the plan in one go. Every element needs an id. The plan keeps the draft's own id.
plan_draft_renderLook at a map draftvueAccès : contributions:writeRender a draft as a PNG image, one level or all of them side by side, exactly as the published plate will look, plus the list of anomalies to check (overlapping rooms, rooms outside the extent, doors off a wall, markers to unknown places).
plan_draft_submitSubmit a map draftmodifieAccès : contributions:writeSend the draft as a contribution to the place's maps: published right away for trusted contributors (level 3+), reviewed by the community otherwise. The preview image is rendered and stored, and the draft is closed. Asks the user to confirm first.
plan_draft_discardDiscard a map draftmodifieAccès : contributions:writeDelete a draft that will not be submitted.
Les recherches renvoient au plus 50 résultats par page. Un panier tient au plus 50 lignes. Un joueur garde au plus 10 brouillons de plans, effacés après 7 jours sans modification. Les contributions suivent les mêmes règles que sur le site (propositions en attente, relecture par la communauté).
L'usage doit rester raisonnable, comme le prévoient les conditions générales d'utilisation. Conditions générales d'utilisation
Le site expose aussi une API REST sous /api, celle qu'utilise Nexus App. Elle n'est pas encore documentée et peut évoluer sans préavis : parlez-nous de vos besoins avant de vous appuyer dessus.
Une idée, un besoin, un souci ? Écrivez-nous sur Discord.
Rejoindre le Discord