Providing I understand your query correctly then yes - If you look out for "Announcement bits" it indicates that the route is being consumed by a protocol. If you don't see the "Announcement bits" field then there are no protocols consuming the route - however, you still might see the field in certain scenarios.
The following indicates the route is being consumed by BGP(3-BGP_RT_Background) and is used for route resolution(4-Resolve tree):
darth@vader-mx80# run show route 10.0.255.3/32 detail
inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
10.0.255.3/32 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface, Next hop index: 0
Address: 0x5490fd0
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS: 65003
Age: 2w6d 8:56:53
Validation State: unverified
Task: IF
Announcement bits (2): 3-BGP_RT_Background 4-Resolve tree 2
AS path: I
The following I have deactivated bgp process and you can see the "Announcement bits" field is omitted:
darth@vader-mx80# run show route 10.0.255.3/32 detail
inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
10.0.255.3/32 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface, Next hop index: 0
Address: 0x5490fd0
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS: 65003
Age: 2w6d 8:57:12
Validation State: unverified
Task: IF
AS path: I
Hope this helps 🙂